``Functions contained in the /functions directory at the project's root will not be included in the
Functions contained in the /functions directory at the project's root will not be included in the deployment
Swhats stopping you from writing +server.ts endpoints?
Cjust learning that now, i (and all the AI's) were under the impression it followed the pattern of the functions folder set up. Nothing is stopping me, just new to pages and wasn't aware as this is the first mention of this difference on that link. searching the internet everywhere else I couldn't find that note.
SPages is a bit a hacky concept imo. Maybe why this exists now https://developers.cloudflare.com/workers/frameworks/framework-guides/svelte/
Cloudflare Docs
Create a Svelte application and deploy it to Cloudflare Workers with Workers Assets.
Cyeah that's where i found it. In my sunday experiment i had set up svelte pages without functions and then created a worker backend. But i was running in to CORS errors over and over again, so i thought maybe just using the functions feature (that i thought was available consistently on all pages frameworks) would be the way to go which then...destroyed me sunday
Scloudflare is very different to many other services i agree its a hard learning curve at the start
Cbut the irony is 2 minutes after i posted the question, i found that link. But still...it should be more front and center and wrangle IMHO should perhaps have a console error that says "we noticed a functions folder, please note svelte wont recognize this folder and yo must do it like ...., please refer to this example...."
Cthat would be easy...save developers HOURS.....if any cloudflare employees are watching this...
Spages really is meant to just use the framework i feel like
Swith worker with assets you could easily bind a functions folder
Ccan you explain what you mean by that?
C(i might be less advanced in my framework/worker expeirence)
Ahttps://developers.cloudflare.com/workers/static-assets/ Pages will eventually merge into Workers (not for a long time probably, at least Pages is unlikely to “stop working” for a long time would be my guess), and you can serve static assets from Workers now (in beta). You can use frameworks too, same as pages. See https://developers.cloudflare.com/workers/frameworks/framework-guides/svelte/ for Svelte. Either way you won’t need the functions folder, as if you’re using Svelte, just use its approach for server-side endpoints.
Cloudflare Docs
Create full-stack applications deployed to Cloudflare Workers.
Cloudflare Docs
Create a Svelte application and deploy it to Cloudflare Workers with Workers Assets.
Cnoted. I used svelte because grok suggested it for my small idea. I wanted something to practice with because i wanted to eventually convert a full django project i created in 2017 into a cloudflare workers/pages project instead of having to maintain this server and upgrade pythong and django etc.
Cbut maybe svelte was a bad choice to learn on
Cyou have way more experience with workers/pages, do you think moving django social bookmarking site built via in 2016 from pinax/django to a cloudflare site is a good idea, or will it cost a lot more to host in the long run and i should just update the django and python code and move it to a new server on say digital ocean
K
Cloudflare Docs
Learn about the limits associated with Browser Rendering.
SWhen i generate my types using
is this expected when just using
wrangler types --experimental-include-runtimeis this expected when just using
nodejs_alsI have no experience of Django I’m afraid 
Svetle is a pretty easy framework to pick up though, I would say. And when using AI, just treat it as a standard Svetle app, for the most part that will work as the Cloudflare Pages adapter handles translation from Svetle -> Cloudflare. Only caveat will be if you use bindings to connect to databases and stuff on Cloudflare,
Svetle is a pretty easy framework to pick up though, I would say. And when using AI, just treat it as a standard Svetle app, for the most part that will work as the Cloudflare Pages adapter handles translation from Svetle -> Cloudflare. Only caveat will be if you use bindings to connect to databases and stuff on Cloudflare,Ci have a good amount of expeirence on a past project with workers and D1/KV but haven;t been keeping up with the new stuff you just linked me too. In the past workers project it was using kv-asset-handler , is https://developers.cloudflare.com/workers/static-assets/ replacing that for some things?
Cloudflare Docs
Create full-stack applications deployed to Cloudflare Workers.
AI believe so, yes. Static Asset Workers effectively store the assets in KV under the hood. I think using Pages is fine for what it’s worth, considering Static Asset Workers are in beta, and there’s probably a bajillion sites using Pages, so they aren’t just going to suddenly kill it (well, I would be very shocked )
)Cshould i update my current project using kv-asseet-handler to static asset workers? Do you know of a tutorial or how to do to that?
AIt’s pretty simple to setup, docs are linked above - effectively you designate a folder as containing your static assets, and some config in wrangler.toml, and any request to a path matching a static asset will be served
Cand that is safe to say will be the future moving forward?
AYes, Pages & Workers are merging gradually, and Static Asset Workers are effectively going to replace Pages in the long run, in short
Mare there any options to connect from workers into a private network? getting tired of seeing bots trying to brute force an API from my k8s cluster that i only access from workers
HUse a tunnel, put it on a subdomain, and then add a firewall that blocks all requests not from a Worker on your zone: https://developers.cloudflare.com/ruleset-engine/rules-language/fields/reference/cf.worker.upstream_zone/
Cloudflare Docs
Identifies whether a request comes from a worker or not.
Soh yea i wondered about that too.
i have 1 public api endpoint in my sveltekit app. is there an easy way to block access not from the same worker? just to reduce possible spam
(preferably in code, not a custom firewall rule)
i have 1 public api endpoint in my sveltekit app. is there an easy way to block access not from the same worker? just to reduce possible spam
(preferably in code, not a custom firewall rule)
Pbelieve you could use an Transform Rule to add the value of
cf.worker.upstream_zone
SHm i did look into that but i dont see any way of "selecting"
cf.worker.upstream_zonethe rule would be something like this
S'cf.worker.upstream_zone' is not a valid value for expression because the use of field cf.worker.upstream_zone is not allowed:bibicat:
Pah right, I believe there should already be an
CF-Workerwhich has the same value as the upstream_zone one
Sthat would only appear if my server side (worker) is requesting the API tho right?
in my case the browser also requests that api endpoint. maybe mTLS is actually what im looking for?
in my case the browser also requests that api endpoint. maybe mTLS is actually what im looking for?
Pyep it would only appear if the request comes for a worker, which could be yours or someone else's
SOkay good to know i will definitely need this for another project. But in this case i guess its fine to just allow access to it
1Will there ever be an option for higher memory Workers?
I know CF is always upgrading their servers but do those performance upgrades make their way to V8 isolates in a meaningful way? Does 1ms of CPU time now do markedly more work now than 1ms of CPU time 3 years ago?
I know CF is always upgrading their servers but do those performance upgrades make their way to V8 isolates in a meaningful way? Does 1ms of CPU time now do markedly more work now than 1ms of CPU time 3 years ago?
1Just some general thoughts I was having. I have reformatted to correctly match my thinking of those being two thoughts separate to each other
AI’d say it’s more likely the upcoming container product will allow you to have more / tune memory rather than Workers raising memory, but no info yet on whether that will be possible afaik
SJust double checking. It has been mentioned that worker assets are cached even tho its not shown. Means even images having
public, max-age=0, must-revalidatei really cant get Build Environment variables to work when i put them in my wrangler config. i usually set them in the dashboard but id like to have some default ones in there like node_version. i tried
varsenv production
AHey, I am using cloudflare workers and I noticed my workers are getting requests for a bunch of routes like
I do use the WAF managed rules: Cloudflare Managed Ruleset, Cloudflare OWASP Core Ruleset, and
Cloudflare Leaked credentials Check
Do you know how I can make sure cloudflare blocks these suspicious requests?
/js/.env/aws.yml/config/settings.prodI do use the WAF managed rules: Cloudflare Managed Ruleset, Cloudflare OWASP Core Ruleset, and
Cloudflare Leaked credentials Check
Do you know how I can make sure cloudflare blocks these suspicious requests?
Pevery public site will get random crawlers/bots that will hit all types of endpoints/paths to see if they can dig something up
Psome of the managed ruleset WAF rules cover the very common ones, but not necessarily all possibilities out there
AI would expect the CF WAF to block .env requests 
AWe have enterprise plan, and we use our own domain
A
AThat's why I'm wondering what I am missing
Acause /config/settings.prod why not let it slip, but
**/.envActually, the core ruleset is not enabled? It's just logging
