Cloudflare Developers•3y ago

I get this on chrome, firefox, and edge...weird

VVictor I get this on chrome, firefox, and edge...weird

Lake•7/19/23, 7:59 AM

have you tried as a incogito? maybe your sessions are in a invalid state?

VVictor I get this on chrome, firefox, and edge...weird

Erisa•7/19/23, 8:54 AM

I 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

Erisa•7/19/23, 8:58 AM

Raised

VVictor I get this on chrome, firefox, and edge...weird

Erisa•7/19/23, 11:03 AM

This should be fixed now, thanks for the report! (and thanks @Walshy for fixing it MeowHeartCloudflare

)

Farhian•7/19/23, 2:47 PM

Hi 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!

Unsmart•7/19/23, 2:50 PM

The 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.

Farhian•7/19/23, 2:51 PM

Yes, we currently are using the Preview as you indicated for each PR and then the production would be once the PR is merged.

Farhian•7/19/23, 2:53 PM

But 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.

Unsmart•7/19/23, 2:56 PM

You 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

Farhian•7/19/23, 2:58 PM

ok 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!

Ashley•7/19/23, 3:19 PM

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 stagingstaging in parallel (stagingstaging 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.devthe-branch.your-project.pages.dev). For the staging deployment, you just need to pass the branchbranch 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.

Ashley•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)

Ashley•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.

Ashley•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

Ashley•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: