N
A
J
A
A
WAWAAAWAWWWWAAWAAAA
W
TAAWA
P
I set up my first prototype project via pages and I'm satisfied that I got it running. However, my journey was a bit bumpy and I'm asking for input for some decisions I made:
wrangler.tomlnpx wrangler pages download config <PROJECT_NAME> to set it up automatically. That also added env vars that I already set up via the dashboard. As far as I understood it, I can't just ignore this file on git since it is needed for the automatic builds. I simply deleted the variables for now. I didn't dig too deep into it but as long as I don't set up other workers which need the vars I should be good for now, right? I also assume there are other ways to use the vars to support open source projectsNexample.com/docs/num and there's a doc with the num 404 naturally (docs/404.html) which wasn't indented to be the 404 page not found. I was debugging why navigating to a doc page with a doc num that doesn't exist showed the page of the doc with the num 404 since I already have a custom 404 page not found in the root level of the website and was trying to fix that before discovering that cf pages has a 404 code custom page support for subdirs too. Now I will let this (feature-not-a-bug) as it is cause this is the best 404 page I've ever seen.
Μ
J
KΜJJJ
Fdash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).KJKKJJKJK
npx wrangler pages download config <PROJECT_NAME>example.com/docs/numdash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_IDa398d794-7322-4c97-96d9-40b5140a8d9b