hey so I have a CNAME for www, and a page rule, and it still effing times out on www for some stupid
hey so I have a CNAME for www, and a page rule, and it still effing times out on www for some stupid reason
HTo confirm, you want it to redirect from
www.zach.handley to zach.handley(assume the domain is your actual domain)?
Zyeah so jonathansogunquit.com is my step fathers site for his restaurant I made, and www.jonathansogunquit.com times out with a 522 for some reason (immediately, might I add) despite having a CNAME and a page rule
Z
Zidk why the hell it's giving a timeout error, I think that's the most upsetting right now, because first of all wrong, it's not timing out, cloudflare is just wrong, and second, it makes ME look bad for cloudflare's error
Znothing in the function logs either when I live stream it and try to access
Zon my browser it works fine, on mobile it times out instantly. don't know why on that front either.
Zmmkay, well, in order for mobile to not timeout, you have to add the www as a custom domain in addition to the other. You can't use a CNAME by default like every other. that should not be the case IMO.
HCloudflare Docs
Learn how to redirect a www subdomain to your apex domain (example.com).
Zyeah so I used pages
Zand added a custom domain
Zand then added a
www -> apex domain, but it needed to be www -> cloudflare pages domainZimo that should be offered when adding a domain, by default, because that was awful and made me look like an idiot, when normally that's what I'd do and then handle it via the Nginx
Zmaybe I am one, but I'd love a little bit of idiot-proof-added if possible, not that it really matters anymore haha
HI'm confused, redirecting
www -> apex doesn't directly involve Pages at all. You just need a dummy record, and a Redirect RulwZthe www needs to be pointed to the pages domain
Zand old people still use it
Zso to me that's either something that should be put in as an option when adding a custom domain or
HOk, I'm even more confused now. If I visit
www, should I be redirected to the apex? What if I visit the Apex? Should I be redirected to www? Should both be serving the same content, without any redirects?
KVery 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()XI 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
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, you are redirected to zach.handley, which serves your Pages project
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
