Hi, I have a durable object running locally and a pages project which want to link to that durable o
Hi, I have a durable object running locally and a pages project which want to link to that durable object, how can I set up these locally?
PThe binding documentation seems all target to already online functions, seems like no local dev environment mentioned
HStart a dev session for the Worker that declares the DO. Then start the Pages Dev session with the flag
—do BINDING_NAME=DoClass@WorkerName
PWow!!! Thanks, this is a huge boost for me!!! It worked!
UI have been trying to increase # of builds per month for pages since months.
No response from increase via form request.
How to get it done guys?
No response from increase via form request.
How to get it done guys?
EI use https://giscus.app/
EYeah it mainly works for dev focused blogs
KIs there anyway to upload source maps to Sentry on pages build?
pages-helpIs there anyway to upload source maps to Sentry on pages build?
pages-helpIs there anyway to upload source maps to Sentry on pages build?
W
Wwhat's the pages.dev?
Wgo for it
W
yes pls send pages.dev
Wmy teammates were ahead of me
CPlease don't ping employees for unreleated issues.
JHello! Is there a way to upload a single asset (for example a json file) to an app? Or is the wrangler command
wrangler pages publish <OUTPUT_DIRECTORY> only meant to send the entire app assets and will upload the entire directory?CWrangler will only upload changed files but you run the publish comment each time. It's how Pages keeps track of deployments incase you need to rollback
Jthank you!
AIs there a way to have multiple custom domains for a Pages project, with one not pointing to production?
e.g. I have something.mydomain.com -> master
Then something-staging.mydomain.com -> a branch
As we deploy master deploys to production and staging, and typically have "friendly" URLs in front. I know CF generates us branch-based aliases, so we could use those for staging, but we'd like it to be as close to production as possible, so use the real domain.
We tried adding the second, but the screen that follows suggests updating the CNAME to point to production (we have it set to point to the staging branch)
e.g. I have something.mydomain.com -> master
Then something-staging.mydomain.com -> a branch
As we deploy master deploys to production and staging, and typically have "friendly" URLs in front. I know CF generates us branch-based aliases, so we could use those for staging, but we'd like it to be as close to production as possible, so use the real domain.
We tried adding the second, but the screen that follows suggests updating the CNAME to point to production (we have it set to point to the staging branch)
AAh this is helpful, thank you - I just noticed it only works on Cloudflare's DNS though, and we're using external DNS, so I'm guessing we just have to use the CF-generated URL for now?
FPages is unlimited free for being Static pages? (Which can use iframes, etc) as opposed to Workers with their 100k daily limit for backend script execution? 
CCorrect.
Wyep 
Li just wanna say how cool it was to find out that cloudflare will prefer PNPM if i have the appropriate lock without additional configuration.
Sadly however, PNPM locks have versioning and my local version of PNPM was out of date
Sadly however, PNPM locks have versioning and my local version of PNPM was out of date
VUnder the functions tab in the dashboard of any pages project, is it a known issue to get 404 on https://developers.cloudflare.com/workers/platform/compatibility-dates.json
VChrome and firefox give me 404 but tor works??
Lthis link works for me on Firefox, if that helps at all 
VI get this on chrome, firefox, and edge...weird
Lhave you tried as a incogito? maybe your sessions are in a invalid state?
EI seem to be getting the 404 page around half the time and the json the other half.. let me raise this to the docs team
ERaised
FHi guys, I'm new to Pages (and Cloudflare in general) so this might be a silly question: I have a web application currently deployed to a Cloudflare Page (pushed from a GitHub action). That is working great. Part of our CICD process, we want to create diff environments: dev, staging, production. Based on certain rules, we would promote from one env to the other (the regular thing ). So the question is: would we need to create separate Pages in Cloudflare or do Pages have a concept of diff environments? (Azure has this thing called 'slots' for a web app deployment). So our app would be hosted at: "dev.myapp.com", "stage.myapp.com" or "myapp.com". Thank you!
). So the question is: would we need to create separate Pages in Cloudflare or do Pages have a concept of diff environments? (Azure has this thing called 'slots' for a web app deployment). So our app would be hosted at: "dev.myapp.com", "stage.myapp.com" or "myapp.com". Thank you!
UThe way pages works theres 1 local env (dev), and 2 deployed envs (preview and production).
The preview env you normally do a deploy for every PR you have and each PR will get its own URL.
The production env you would merge the code into your master branch.
The preview env you normally do a deploy for every PR you have and each PR will get its own URL.
The production env you would merge the code into your master branch.
FYes, we currently are using the Preview as you indicated for each PR and then the production would be once the PR is merged.
FBut if we want to have diff deployments (dev, stage and prod), I assume that we would create 3 diff Pages, correct? For example, we want to have the Dev enviroment which contains all teh latest changes that are pushed to main. Once we are happy with those, we want to push dev to stage and stabilize, make sure eveything is working great and all that. Once we are happy, we would promote stage to Prod.
UYou can still do something with 1 pages project for that but I dont get into that as its pretty unnecessarily complicated so no clue how you do that 
Fok sounds good, thank you! I'll use 3 pages for now (since I know how to do that) and then update later if needed Thank again!
I'll use 3 pages for now (since I know how to do that) and then update later if needed Thank again!AJust on this above @Farhian, what we've done is created protected branches for the environments, and rather than using the Pages Git integration, we use https://github.com/cloudflare/pages-action and set the branch. So we deploy
The protected branches is just to prevent anyone branching and pushing to that branch
And we just set them to read-only.
main to production and staging in parallel (staging is a protected branch name in our repo). And Cloudflare will create consistent, branch-based .pages.dev URLS (e.g. the-branch.your-project.pages.dev). For the staging deployment, you just need to pass the branch parameter when running the action.The protected branches is just to prevent anyone branching and pushing to that branch
And we just set them to read-only.A(fwiw, the GitHub Action is also significantly faster than building/deployinh on Cloudflare - not that Cloudflare is slow, but GitHub is quicker as it doesn't do things like install Node each time etc. - we saw build times of ~4mins or so using the Git integration, around 1 min using the Action)
