Then your `www` doesn't need to be connected to Pages at all. You give it a dummy record, add a redi

Then your

www

www

www

www doesn't need to be connected to Pages at all. You give it a dummy record, add a redirect rule, and then when you visit

www.zach.handley

www.zach.handley

www.zach.handley

www.zach.handley, you are redirected to

zach.handley

zach.handley

zach.handley

zach.handley, which serves your Pages project

HHello, I’m Allie!Then your `www` doesn't need to be connected to Pages at all. You give it a dumm...

ZachHandley•3/9/25, 7:35 AM

k. 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

lorde•3/9/25, 10:11 AM

Hi 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,

Walshy•3/9/25, 10:52 AM

You're trying to deploy a Pages project in Workers CI?

Walshy•3/9/25, 10:52 AM

You should use Pages CI for Pages

Walshy•3/9/25, 10:52 AM

But 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

Mad•3/9/25, 9:01 PM

how 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.

MMad how do I set env vars globally inside my workers? these env vars are used by som...

Avilaa•3/9/25, 9:04 PM

One 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

Mad•3/9/25, 9:06 PM

the library might be getting loaded before that. moreover, the process object is unavailable inside worker?

Mad•3/9/25, 9:07 PM

I am not using the hono framework, directly using the project setup by wrangler CLI

Mad•3/9/25, 9:14 PM

hey, it worked!! I added the node types, which allowed me to set the

process.env

process.env

vars. Also, I set the vars immediately inside fetch.

Mad•3/9/25, 9:14 PM

thanks @Avilaa

MMad thanks @Avilaa

Avilaa•3/9/25, 9:27 PM

With pleasure

AcidWeb•3/10/25, 6:51 AM

If 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?

Avilaa•3/10/25, 8:39 AM

What is the price/limit of using websocket without durable objects?

SuperHelpflare•3/10/25, 9:39 AM

Please 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.

milan•3/10/25, 4:01 PM

I'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

Mmilan I'm trying to wrap my head around what's the pros and cons of Pages and Workers;...

Silvan•3/10/25, 6:26 PM

related to your first question. maybe this helps pages-discussions

Silvan•3/10/25, 6:38 PM

i 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/ ?

Cloudflare Docs

Redirecting www to domain apex · Cloudflare Pages docs

Learn how to redirect a www subdomain to your apex domain (example.com).

Walshy•3/10/25, 6:39 PM

yes follow that doc

B1397KB•3/11/25, 10:14 AM

Hey guys, How do I add a CPU time limit to the toml configuration file for Worker Paid Plan? What are the specific fields?

Walshy•3/11/25, 10:15 AM

https://developers.cloudflare.com/workers/wrangler/configuration/#limits

B1397KB•3/11/25, 10:16 AM

Thanks

0xe83c516•3/11/25, 10:30 AM

Hi, 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?

Avilaa•3/12/25, 12:53 AM

Hi, How many websocket connections can I have per day? and messages (without durable objects)? please

Avilaa•3/12/25, 1:19 AM

Could someone please tell me the prices/limits for API cache and websockets (without durable objects), please, I can't find anything anywhere

RobbBoss•3/12/25, 7:47 AM

I 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!

RobbBoss•3/12/25, 8:13 AM

Given 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.

RobbBoss•3/12/25, 8:24 AM

I 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.

xPaw•3/12/25, 11:51 AM

https://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

Cloudflare Docs

Cache · Cloudflare Workers docs

Control reading and writing from the Cloudflare global network cache.

Walshy•3/12/25, 12:06 PM

Yes it should

RRobbBoss I genuinely wish I had been able to predict this deprecation of Pages into Worke...

Walshy•3/12/25, 12:08 PM

To be clear, Pages isn't going anywhere anytime soon and we will be making the migration between Pages -> Assets easier. A migration guide is in the works and we have no plans to make it a pain, we want to make it as easy as possible.

You can still make Pages projects on accounts today like you could before, you do not need to use Assets, we still see people onboard daily to Pages

RRobbBoss Given that the #pages-discussions channel is now archived, I presume that to be ...

Walshy•3/12/25, 12:10 PM

i wouldn't read into this, we did this for a 2 main reasons:

We are always looking to reduce our channel count - it's the #1 feedback item we get -- "There's too many channels, it's overwhelming"
We are aligning with how we as a platform are structing things, you will see we still have #pages-help and this is also Pages, we just dropped the whole dedicated section to align with the dashboard on a "Compute" section.

Walshy•3/12/25, 12:11 PM

we don't need a workers-discussions and pages-discussions under this section so we just aligned into one.

WWalshy Yes it should

xPaw•3/12/25, 12:13 PM

thanks, another quick q: it seems like workers have a rate limiting api available, but it needs to eb bound in wrangler config, so theres no way to get it in snippets?

Walshy•3/12/25, 12:13 PM

No, Snippets don't have access to bindings at all today

Walshy•3/12/25, 12:13 PM

You would need to use Rate Limit rules

xPaw•3/12/25, 12:13 PM

thats what i do

andifined.dev•3/12/25, 12:18 PM

Since yesterday we always get the error npm too many Open files when deploying using workers auto Build. What‘s curious, we deploy the same codebase to three different Environments but it happens only with one?

andifined.dev•3/12/25, 12:19 PM

Aren‘t able to deploy changes at the Moment.

WWalshy i wouldn't read into this, we did this for a 2 main reasons: 1. We are always lo...

RobbBoss•3/12/25, 12:41 PM

Thank you. I appreciate your insight and kind explanations. This makes sense.

James•3/12/25, 12:59 PM

Fwiw I would still encourage folks to use Assets wherever possible over Pages. Cloudflare will almost certainly never officially deprecate Pages - but you can already see it’s slowly being abandoned, with many bindings still not supported, and the build image tooling versions aging rapidly.

James•3/12/25, 1:00 PM

Pages isn’t going anywhere - but if you’re starting something new, use Assets if you want to play with anything new Cloudflare is releasing. I’d be very surprised if any new bindings get added to Pages at this point.

JJames Pages isn’t going anywhere - but if you’re starting something new, use Assets if...

RobbBoss•3/12/25, 1:00 PM

This effectively confirms that we have to re-tool.

RobbBoss•3/12/25, 1:01 PM

I eagerly anticipate the migration guide. Our project is DOA without it. We have to find a platform asap.

James•3/12/25, 1:01 PM

If what you have today works, you don’t need to. But if you’re looking to use anything new that Cloudflare releases in future, then Pages is not a good choice today sadly.

RobbBoss•3/12/25, 1:02 PM

We put months of work into Pages. It's not future proof anymore, you just confirmed. We cannot launch on it.

RobbBoss•3/12/25, 1:03 PM

Our project is DOA today. We must find a new and more stable platform. It will be Workers if we can figure it out. But if we have to rebuild, well, that is a cost and we will look for stability.

James•3/12/25, 1:03 PM

Sorry, that’s the reality of Pages today. It’s stable and highly functional with the features it has. But it has already been lagging behind Workers and I don’t anticipate that changing.

RobbBoss•3/12/25, 1:04 PM

No, that's fine, it's true. I lamented using Pages to start. I didn't want to, but it was the direction we were pushed in, by Cloudflare's documentation.

James•3/12/25, 1:05 PM

Fwiw moving to Assets should be relatively straightforward. Functions aren’t a thing (which imo is a good move, they were always a weird Pages only thing), but static assets, _headers, _redirects etc. all exist now.

Then your `www` doesn't need to be connected to Pages at all. You give it a dummy record, add a redi

Similar Threads

Similar Threads

Similar Threads