Automate deployment of full cloudflare deploys for staging servers

[danyx23]

Core problem

We have a great setup to automatically provision staging servers for every branch and to update them on every code push - but there is one part that is not automated yet and that is deploying to cloudflare staging environments. Since we are relying on cloudflare more and more it would be great if we could automate this too.

Proposed solution

Just like we have the option to use -algolia in our branch names and get an algolia index provisioned it would be great if we could include something like -cfstaging in a branch name and then we'd get a fully functional cloudflare staging setup.

This should entail:

• Baking the content (at least grapher pages, probably more) with the staging server url (so that redirects or the download links etc work as they would on prod)
• make sure to exclude files that are too big ("There's currently an unofficial step in the deployContentPreview script, where you have to run rm ~/live-data/bakedSite/assets-admin/admin.mjs.map because the file is over 25MB which is CF Pages' limit.")
• Do the logic that is encoded in the ops/buildkite/deploy-content-preview script (this needs a decision whether we want to deploy staging sites behind cloudflare auth or not)

Alternatives

Keep deploying it manually

[larsyencken]

@Marigold Adding this one to your cycle