this link works for me on Firefox, if that helps at all <:shrug:1086052484864286840>
this 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.
mainstaging 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)
ANaturally you don't have to do that in parallel, you could have it deploy to each stage one-by-one using different Actions
UPages uses an internal cache instead of the main CDN cache. You should disable cache on any pages domain.
Uyoure in the wrong channel, this channel is about cloudflare pages
U
KYou'd be correct, nothing like that is available.
FThank you! That is a good idea! We are also using the pages action and are pushing from GitHub.
AAh nice, then it should be nice and easy rather than having to migrate 
FSo do you always push to main after merging a PR for example?
FOr do you integrate from time to time from the stage branch?
AYeah, we always merge to main, as our flow is PR -> merge -> deploy to staging and production, but I don’t see why it wouldn’t work with a stage branch if that’s your flow
AWhere is the best place to disable caching for a domain the serves content from pages?
I tried using Cache Rules, but I get this error message
I tried using Cache Rules, but I get this error message
EWhat rule are you creating that causes that error?
A
CWhat does your hostname look like? I have this rule which saves fine
Ajust
www.mydomain.com and mydomain.comESeems very odd
Ahm. creating a new rule worked, but editing an existing one does not
ELooks like it happens if you take a "Eligible for cache" rule and edit it into a "Bypass cache" rule
EWithout first removing the settings that were set under the eligible
Abasically, i had an old cache rule on the domain that I set up the other day forgetting I should bypass the cf cache for pages. It just set a edgettl cache for a specific URI. I then tried to edit that rule to the one I sent above
here is what it was before:
here is what it was before:
EYep
ELike I thought
ECool
Asorry i took a min to send what it was before 
SRandom fun question, what is the most builds of any project on Pages?
SOne of mine is about to hit 7k
Ktens of thousands
CIt's fun at somepoint the API just times out so you have no clue
Werr like 80k?
CPages doesn't offer log push or tail consumer bindings, correct?
Wcorrect
W
C