i don't think that you understand how pages works, when you do next build and next export, you write
i don't think that you understand how pages works, when you do next build and next export, you write content to kv and save it there
KAnything you do in the build process & write to your output folder will be available when deployed but not for you to fetch in any manner like
fs
Kyou can use functions to store content in kv i think
Ainteresting. so CF Pages is writing to KV by default? or is this something we have to do during the build?
Ayeah, if I have the mental model wrong for how all this is supposed to work, no goody
Kbuild command -> throws stuff to
/output-folder -> /output-folder contents are deployed globally (KV)Kif present,
/functions folder -> built into a Worker -> ditto, deployedKvastly simplified but you get the idea
Kthere is no environment for your own 'server' as such - just Workers & KV
Aso we can write to global output folder after build then?
KNo
KThere is no 'folder' after the build process is done
KThe KV is abstracted away from you
Aah ha, ok, abstracted away
KAny dynamic functionality you want after building your static assets has to be done with Functions
Kso you could have your own KV, sure
Aclient creates new URL, content at URL is stored in KV, Function retrieves that content to serve new page back to client
KIf that's how you want your site to work, sure
KFunctions are only required if you want dynamic content
KIf you just have static pages and assets, the build process handles everything
Ki.e your site has something where users can make their own blog posts - you could store that content in KV & have a function for your
/posts page that fetches them all & renders themAyes, it is a dynamic site, and now I am at a junction, deciding if I keep with CF pages or try deploying to a different platform where
next start and ISR/SSR work out of the boxAthanks for the info, at a crossroads here.
One more question please. During the build, is there a way to access Functions?
One more question please. During the build, is there a way to access Functions?
next buildFunctions are built in the build process so not that I am aware of - but I've also never used
next
Aok, thank you
IThere's not because at the point of the build the Functions don't yet exist.
KYour Functions folder is built into a Worker and then deployed alongside your Pages project in general - although I think some frameworks just turn it into a
_worker.jsWhat you can do is run some Javascript as part of your build step.
IYeah, SvelteKit does that. Next.JS isn't support yet though 
Ai see, i see, thanks for the insight
SI'd suggest maintaining at least one old version at all times to avoid such things. Also having a versioned API (if you have any) will eliminate these scenarios (in most cases).
WWhat do you mean?
WHave you added it to custom domains?
INope, the subdomain is what you need to enter.
IBut do you have an A record on that same subdomain?
IYeah, that should be fine then. Main domain records don't affect the subdomain (or they shouldn't anyway).
ICan you try clearing your DNS cache?
INope, it will be locally on your computer.