Very simple question: can I just straight up upload a node.js website to cloudflare workers or do I
Very simple question: can I just straight up upload a node.js website to cloudflare workers or do I have to change something?
BYou'll almost certainly have to change something. At the very least it needs to be bundled into a single JS file which exports a fetch handler: https://developers.cloudflare.com/workers/runtime-apis/handlers/fetch.
Beyond that, it depends entirely on the implementation of your site. Workers supports many but not all Node.JS APIs. I'm guessing your Node.JS site uses
Beyond that, it depends entirely on the implementation of your site. Workers supports many but not all Node.JS APIs. I'm guessing your Node.JS site uses
fs
KIt's a very simple app, a budget manager. If by fs you mean the website has file upload/download support, the only file related option there is a .csv export of the table data.
HI just upgraded the zola version to 0.20.0 but getting the error as in the picture
H
HI am using Cloudflare pages build system 1
HOh I forgot, Happy Weekend! Don't forget to take some time for yourself
XHas anyone ever attempted to serve hashed assets from previous deployments in the current deployment? As an idea to fix issues where a dynamic route's JS file doesn't exist anymore at the main domain after a deployment, but where a user might already have the website open
WAs part of Pages or Workers Assets?
XPages, which seems to be the issue
WPages, you cannot
Workers Assets, you'd need to run the Worker first and use
Workers Assets, you'd need to run the Worker first and use
env.ASSETS.unstable_getByETag()I can omit the static assets from _routes.json for my worker to hit it, but then I don't see a way to then serve it
XGotcha. Sounds like a better idea might be to try tweaking the build so it uses an absolute URL to the deployed version for those assets
WYeah or implementing a catcher and serving a nice page (or force refreshing) - less than ideal though
WBeen thinking of how we just solve this in Workers Assets
XAn ideal UX from my point of view is the ability to configure some paths that "fall through" to previous deployments I suppose
WWill note that down :)
XThanks for the chat!
XI'm not actually sure I could even inject the deployment host before my assets, given that it is seemingly a random hash that will only be produced after I've already uploaded the files in which I'd like to insert said hash?
Edit: I solved this by associating my releases with the deployment ID in KV, and then proxying the assets to a 301 with the permanent URL using that release and the stored deployment ID In KV
Edit: I solved this by associating my releases with the deployment ID in KV, and then proxying the assets to a 301 with the permanent URL using that release and the stored deployment ID In KV
Zredirected to apex
HThen your
wwwwww.zach.handleyzach.handley
Zk. well all I was saying is that's a silly solution, to have 4 separate articles and me needing to come here to finally figure it out, when like, it could just offer to add it lol. thanks for the help regardless
LHi all, I'm encountering an issue with my build,
here is the permission fort he token I'm using and the error I'm getting,
the account also has all the permissions,
here is the permission fort he token I'm using and the error I'm getting,
the account also has all the permissions,
WYou're trying to deploy a Pages project in Workers CI?
WYou should use Pages CI for Pages
WBut either way, the API token doesn't have Pages edit which is why it fails. Though, I don't know if adding that will make it succeed since again, diff product
Mhow do I set env vars globally inside my workers? these env vars are used by some libraries I am running within workers. The libraries don't provide a way to override the value via params so I need them to be available as env vars.
AOne option is to set process.env yourself from a middleware, with hono:
app.use((c, next)=>{
process.env.var = c.env.var;
next();
}); I don't know what other forms exist
app.use((c, next)=>{
process.env.var = c.env.var;
next();
}); I don't know what other forms exist
Mthe library might be getting loaded before that. moreover, the process object is unavailable inside worker?
MI am not using the hono framework, directly using the project setup by wrangler CLI
Mhey, it worked!! I added the node types, which allowed me to set the
process.envthanks @Avilaa
AWith pleasure
AIf I have an API fully powered by Workers and that API sends files to users from non-public R2 buckets, what is the correct way to handle traffic from multiple regions? Should I make a bucket per region and decide which bucket should be used on the worker level?
AWhat is the price/limit of using websocket without durable objects?
SPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
MI'm trying to wrap my head around what's the pros and cons of Pages and Workers; it seems to be that Pages are being slowly replaces/assimilated into Workers, functionality wise so I guess the way forward is to use Workers only?
related to that, I want to deploy a rather simple (to start) project - web frontend built in React and an RESTful API (maybe using Hono, maybe just raw-dogging it) and I want to have it in a monorepo, but not sure how to structure it - should I have two "packages" with their own wrangler.jsonc (that way they'll be deployed independently, right?) or is there a way how to have it all under just one package? does anyone have some links to github repos I could use as a reference? the only ones I could find so far are very basic
related to that, I want to deploy a rather simple (to start) project - web frontend built in React and an RESTful API (maybe using Hono, maybe just raw-dogging it) and I want to have it in a monorepo, but not sure how to structure it - should I have two "packages" with their own wrangler.jsonc (that way they'll be deployed independently, right?) or is there a way how to have it all under just one package? does anyone have some links to github repos I could use as a reference? the only ones I could find so far are very basic
SSi was wondering what the "best" approach is to get www working when using a custom domain in my worker?
Would it be this https://developers.cloudflare.com/pages/how-to/www-redirect/ ?
Would it be this https://developers.cloudflare.com/pages/how-to/www-redirect/ ?
Cloudflare Docs
Learn how to redirect a www subdomain to your apex domain (example.com).
Wyes follow that doc
BHey guys, How do I add a CPU time limit to the toml configuration file for Worker Paid Plan? What are the specific fields?
BThanks
0Hi, I was wondering how a worker codebase (TS) should be structured, more specifically how one would have multiple workers, can I just have different exports? I somehow can't find anything about this in the docs -- is the idea to give each worker its own codebase?
AHi, How many websocket connections can I have per day? and messages (without durable objects)? please
ACould someone please tell me the prices/limits for API cache and websockets (without durable objects), please, I can't find anything anywhere
RI recently tried the fun misadventure of taking my Pages site and putting it into a new account, which I didn't realize I had started the project as a Workers Assets project in the new account.. and lost a day trying to make that work. I eventually decided to start a new project in the new account and manually port everything over into the new working Astro project in the new account. I understand that this is definitely not the place to ask for an account->account site migration tool, that would be awesome, but this is not that place... so...
Because clearly Astro projects that were started on Pages will not run on Workers Assets just out of the box, and finding the new config differences is... opaque.
Is there a guide anywhere regarding moving a project from Pages to Workers Assets?
Thank you in advance for your help and insights!
Because clearly Astro projects that were started on Pages will not run on Workers Assets just out of the box, and finding the new config differences is... opaque.
Is there a guide anywhere regarding moving a project from Pages to Workers Assets?
Thank you in advance for your help and insights!
RGiven that the #pages-discussions channel is now archived, I presume that to be a tacit "Yes. Pages are now deprecated" answer. Thank you, that is a very relevant reference in this light.
RI genuinely wish I had been able to predict this deprecation of Pages into Workers Assets so many months ago when we designed our architecture... I did not realize how dependent we were on Pages specifically, and how disruptive it could be to lose the thing. I guess I knew that Pages have been running on Workers all along, so I didn't anticipate this could be so problematic, and I didn't think Cloudflare wouldn't have a migration guide at all in the event they decided to just end Pages, which they seem to be doing. I guess there was a reason it took Python 10+ years to deprecate Python 2.
We have an unconventional use case due to subdomains and DNS rules in coordination with Workers and Pages both and it's difficult to port without big effort, which we are having to undergo because we need to migrate to a separate account from the original developer's personal account. This is not a common use case in Cloudflare we are finding, or else there would be faculties for it. This seems like a strange oversight, to move a zone or site to a new account seems like it would be more common, but I can see how it's necessarily complex.
We are reconsidering Cloudflare dependency now. We are almost definitely not leaving Cloudflare, but it would be idiotic not to make a go-kit so to speak, and our CTO does have us pricing alternatives and designing migration and mitigation strategies. Uncertainty is bad. I can't place that blame on Cloudflare entirely maybe even at all, I simply don't know right now, but it's funny in the linked discussion there was a reference to bun 1.2 in the end there. And the argument against maintaining up to date bun support in Pages was that bun breaks backwards compatibility too frequently. I find that ironic in this case. I don't use bun for this reason, too.
Please forgive me if this is not relevant here, but it seemed directly relevant to discussion about Workers and Pages. I'm open to instruction and direction. Thank you.
We have an unconventional use case due to subdomains and DNS rules in coordination with Workers and Pages both and it's difficult to port without big effort, which we are having to undergo because we need to migrate to a separate account from the original developer's personal account. This is not a common use case in Cloudflare we are finding, or else there would be faculties for it. This seems like a strange oversight, to move a zone or site to a new account seems like it would be more common, but I can see how it's necessarily complex.
We are reconsidering Cloudflare dependency now. We are almost definitely not leaving Cloudflare, but it would be idiotic not to make a go-kit so to speak, and our CTO does have us pricing alternatives and designing migration and mitigation strategies. Uncertainty is bad. I can't place that blame on Cloudflare entirely maybe even at all, I simply don't know right now, but it's funny in the linked discussion there was a reference to bun 1.2 in the end there. And the argument against maintaining up to date bun support in Pages was that bun breaks backwards compatibility too frequently. I find that ironic in this case. I don't use bun for this reason, too.
Please forgive me if this is not relevant here, but it seemed directly relevant to discussion about Workers and Pages. I'm open to instruction and direction. Thank you.
Xhttps://developers.cloudflare.com/workers/runtime-apis/cache/#headers
Does cache.put support CDN-Cache-Control header (even when Cache-Control is present), or do I have to rewrite CDN-Cache-Control into Cache-Control on the response before putting it into cache (in a snippet)? docs aren't clear on this
Does cache.put support CDN-Cache-Control header (even when Cache-Control is present), or do I have to rewrite CDN-Cache-Control into Cache-Control on the response before putting it into cache (in a snippet)? docs aren't clear on this
Cloudflare Docs
Control reading and writing from the Cloudflare global network cache.
WYes it should
