Just on this above <@247207278027997189>, what we've done is created protected branches for the envi

Just 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

main

main

to production and

staging

staging

in parallel (

staging

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

the-branch.your-project.pages.dev

the-branch.your-project.pages.dev

the-branch.your-project.pages.dev). For the staging deployment, you just need to pass the

branch

branch

branch

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.

AshleyOP•7/19/23, 3:20 PM

(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)

AshleyOP•7/19/23, 3:25 PM

Naturally you don't have to do that in parallel, you could have it deploy to each stage one-by-one using different Actions

Unsmart•7/19/23, 3:33 PM

Pages uses an internal cache instead of the main CDN cache. You should disable cache on any pages domain.

Unsmart•7/19/23, 3:37 PM

youre in the wrong channel, this channel is about cloudflare pages

Unsmart•7/19/23, 3:38 PM

general-help

kian•7/19/23, 5:17 PM

You'd be correct, nothing like that is available.

AAshley Just on this above <@247207278027997189>, what we've done is created protected b...

Farhian•7/19/23, 6:20 PM

Thank you! That is a good idea! We are also using the pages action and are pushing from GitHub.

AshleyOP•7/19/23, 6:20 PM

Ah nice, then it should be nice and easy rather than having to migrate

Farhian•7/19/23, 6:27 PM

So do you always push to main after merging a PR for example?

Farhian•7/19/23, 6:28 PM

Or do you integrate from time to time from the stage branch?

Farhian•7/19/23, 6:33 PM

@Ashley

AshleyOP•7/19/23, 6:44 PM

Yeah, 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

ajgeiss0702•7/19/23, 10:23 PM

Where 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

bypass cache can only be set with BrowserTTL for the set_cache_settings action (Code: 20183)

bypass cache can only be set with BrowserTTL for the set_cache_settings action (Code: 20183)

Erisa•7/19/23, 10:27 PM

What rule are you creating that causes that error?

ajgeiss0702•7/19/23, 10:30 PM

Cyb3r-Jak3•7/19/23, 10:37 PM

What does your hostname look like? I have this rule which saves fine

ajgeiss0702•7/19/23, 10:37 PM

just

www.mydomain.com

www.mydomain.com

and mydomain.commydomain.com

Erisa•7/19/23, 10:40 PM

Seems very odd

ajgeiss0702•7/19/23, 10:40 PM

hm. creating a new rule worked, but editing an existing one does not

Erisa•7/19/23, 10:41 PM

Looks like it happens if you take a "Eligible for cache" rule and edit it into a "Bypass cache" rule

Erisa•7/19/23, 10:42 PM

Without first removing the settings that were set under the eligible

ajgeiss0702•7/19/23, 10:42 PM

basically, 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:

Erisa•7/19/23, 10:42 PM

Yep

Erisa•7/19/23, 10:42 PM

Like I thought

Erisa•7/19/23, 10:42 PM

Cool

ajgeiss0702•7/19/23, 10:42 PM

sorry i took a min to send what it was before

simpson•7/19/23, 11:36 PM

Random fun question, what is the most builds of any project on Pages?

simpson•7/19/23, 11:37 PM

One of mine is about to hit 7k

kian•7/19/23, 11:38 PM

tens of thousands

Cyb3r-Jak3•7/19/23, 11:48 PM

It's fun at somepoint the API just times out so you have no clue

Walshy•7/19/23, 11:49 PM

err like 80k?

Cyb3r-Jak3•7/20/23, 12:33 AM

Pages doesn't offer log push or tail consumer bindings, correct?

Walshy•7/20/23, 12:33 AM

correct

Walshy•7/20/23, 12:34 AM

Cyb3r-Jak3•7/20/23, 12:34 AM

davidentrotree•7/20/23, 1:16 AM

if a new pages deployment goes out for a application, are the old deployments still running?

BKtheInfamous•7/20/23, 6:36 AM

is anyone else having the same problem with deploying a site from your github repo? I press the "connect to github" button on pages and it redirects me onto the github configuration of the cloudflare pages integration which i've already installed and given access to all repos

BKtheInfamous•7/20/23, 6:38 AM

like this part in the setup guide:

Once you have selected a Git repository, select Install & Authorize and Begin setup. You can then customize your deployment in Set up builds and deployments.

Once you have selected a Git repository, select Install & Authorize and Begin setup. You can then customize your deployment in Set up builds and deployments.

like...i can't even get to the "begin setup" page, every time i go back to the pages tab it asks me to connect to github again and redirects me onto the github cloudfare integration page

BKtheInfamous•7/20/23, 6:38 AM

would anyone know how to fix this?