Use versioned Worker previews for branch content

This commit is contained in:
Kevin
2026-09-02 11:01:09 -04:00
parent dfc87b86ac
commit bdf0d06c1a
7 changed files with 59 additions and 17 deletions
+6 -7
View File
@@ -33,13 +33,12 @@ routes, account IDs, or secrets.
## Preview deployment
The Gitea workflows deploy scoped non-production Workers from every non-`main`
branch: `3031023-xyz-www-preview` for primary-site changes and
`3031023-xyz-blog-preview` for blog changes. Relevant primary-site pushes to
`main` deploy the existing `3031023-xyz-www` production Worker automatically.
Relevant blog pushes to `main` deploy the separate `3031023-xyz-blog`
production Worker automatically. Both production workflows deploy static assets
only.
The Gitea workflows upload scoped non-production preview versions of the
production Workers from every non-`main` branch. Cloudflare assigns each branch
a readable `workers.dev` preview alias without changing production traffic.
Relevant primary-site pushes to `main` deploy `3031023-xyz-www`, and relevant
blog pushes to `main` deploy `3031023-xyz-blog`, automatically. Both production
workflows deploy static assets only.
It uses the existing `CF_API_TOKEN` and `CF_ACCOUNT_ID`. The token retains the
Pages permissions needed for the `main` rollback target and now also permits
the non-production Worker preview deployment.