Pages Function seemingly not deployed to base environment
Hi all,
I have a environment that's xxx.pages.dev that seems to get updated every time I run a deploy from the CLI. However, I just bought a simple function and when I run deploy with that included, it successfully deploys to the "new" environment that wrangler produces (https://a2189f60.xxx.pages.dev) but not to my base environment (xxx.pages.dev). All other changes seem to go through this flow but not the function, for some reason. When I try to navigate to my function through xxx.pages.dev/myFunction it seems to just show me the page at the root (xxx.pages.dev). Any ideas?
7 Replies
Sounds like you're deploying to the preview environment (and thus, not available at the production url)
I'd check what branch you're on and what your production branch is
both the branch I'm working on and the prod branch are main
And it's only the function. all other changes deploy to the prod env
It's the same deploy path for everything (since they're all uploaded at once)
If you share a URL I can take more of a look
this is my "prod" url: https://uvuli-esketit.pages.dev/AddEmailToList
env where function was deployed: https://ac617b02.uvuli-esketit.pages.dev/AddEmailToList
yep looks fine to me, uvuli-esketit.pages.dev is serving ac617b02.uvuli-esketit.pages.dev
and both pages also look the same
ahhh ok. Might be a cache issue then. Thanks!