It’s not documented, but it is the one wrangler uses
It’s not documented, but it is the one wrangler uses
LCan I use it?
ZYou can. You do have to look at the wrangler code to figure out how the API works, but there is nothing stopping you from doing that
Lcan you point me in the right direction in the wrangler git repo?
LL
Tis this the end point we should use as REST api for direct upload
https://api.cloudflare.com/client/v4/pages/assets/upload ?
https://api.cloudflare.com/client/v4/pages/assets/upload ?
HNote too that afaik there is also a separate endpoint to finalize the deployment, which you would also have to call
HAnd you can also just upload the HTML if that is the only part that is dynamic, if you have already made a deployment
LYouve been a great help, thank you.
TWe have create a API token and gave it all resources. But when i try POST I get
using this URL https://api.cloudflare.com/client/v4/pages/assets/upload
{"success":false,"errors":[{"code":8000013,"message":"Authorization failed"}]}using this URL https://api.cloudflare.com/client/v4/pages/assets/upload
HIt looks like that API requires a JWT maybe?
TI had to add the account id,
https://api.cloudflare.com/client/v4/accounts/CLOUDFLARE_ACCOUNT_ID/pages/assets/uploadTthanks for the help
Whi how can i add dns domain from other cloudflare account to my pages or worker on my account? is that possible ?
CI've never used Remix but there's an official adapter for Pages maintained by Remix and iirc it's made to run on Edge, so I'd imagine it's pretty good, unlike next.js where its community made and Vercel seems to randomly break things for Edge Runtime every so often lol
ERemix also has its pains. We have to basically dynamic import everything otherwise we hit worker startup script limits.
Also wrangler + remix dev experience isn't great. Really hoping wrangler can support the vite efforts going into remix
Also wrangler + remix dev experience isn't great. Really hoping wrangler can support the vite efforts going into remix
EYou probably need to add
www.lloydatkinson.net as a custom domain on the Pages project (which will update DNS, but its important that you add as a custom domain as well)ENot if you change the redirect like you said, so its going the other way round instead
EI will also note that 301 redirects are permanent by design, if you think you're going to change or remove the redirect in future you should not be using 301 and should be using 302 instead. When you make the change you may find some browsers that have the 301 cached might get confused potentially resulting in a redirect loop. There's not a lot you can do about that except clear cache on affected browsers and remember for next time
EYes
EThen once it works you can remove the other one if you want, it doesnt do anything now that theres a redirect in front
EIt updated the DNS for you, its now pointing to the Pages project 
which is what you want
which is what you wantEYour www site loads fine for me now (it wasnt earlier)
ECNAME is all you need
EWell
EYou can remove the non-www CNAME and replace it with an A if you want it to look clean, it doesn't actually make any difference since the redirect takes priority
EThe current setup is working fine so you can leave it as-is if you want
EIt's working fine from my end
EMy only advice is the cautionary tale about using 301 I mentioned above; if you think you'll ever want to change the redirect in future it's safer to use a temporary 302 redirect instead
EThen no problem!
EYeah www and non-www is a fun topic, there's quite a lot of debate over which one is "best" to use in which situation