Record independent blog deployment verification
This commit is contained in:
@@ -15,3 +15,18 @@ collections and any editor/CMS workflow are explicitly deferred.
|
|||||||
Primary-only content changes deploy only the primary preview Worker;
|
Primary-only content changes deploy only the primary preview Worker;
|
||||||
blog-only content changes deploy only this Worker; shared source changes deploy
|
blog-only content changes deploy only this Worker; shared source changes deploy
|
||||||
both. Each workflow has explicit path filters to enforce that boundary.
|
both. Each workflow has explicit path filters to enforce that boundary.
|
||||||
|
|
||||||
|
## Phase 5 hosted-test record — 2026-09-02
|
||||||
|
|
||||||
|
- Hosted domain: `https://blog.3031023.xyz` is attached only to
|
||||||
|
`3031023-xyz-blog-preview`; it returned 200 with the expected journal title,
|
||||||
|
and an unknown route returned 404.
|
||||||
|
- Shared deployment-boundary update: successful Gitea runs 133 (blog) and 134
|
||||||
|
(primary) rebuilt the two Workers independently from the same commit.
|
||||||
|
- Blog-only content update: commit `4e2d0f8` changed only
|
||||||
|
`sites/blog/site.json`; successful Gitea run 135 deployed only the blog
|
||||||
|
Worker. No primary deployment was created for that commit.
|
||||||
|
- Rollback remains independent: Cloudflare maintains distinct deployment
|
||||||
|
histories for `3031023-xyz-www` and `3031023-xyz-blog-preview`. No live
|
||||||
|
rollback was executed because there was no incident; the primary rollback
|
||||||
|
procedure is documented in `cutover-runbook.md`.
|
||||||
|
|||||||
@@ -0,0 +1,30 @@
|
|||||||
|
# Phase 5 verification — independent hosted subdomain
|
||||||
|
|
||||||
|
## Hosted Workers
|
||||||
|
|
||||||
|
| Hostname | Static Worker | Role |
|
||||||
|
| --- | --- | --- |
|
||||||
|
| `3031023.xyz` | `3031023-xyz-www` | Primary production site |
|
||||||
|
| `blog.3031023.xyz` | `3031023-xyz-blog-preview` | Independently hosted pilot subdomain |
|
||||||
|
|
||||||
|
Neither hosted site uses a hostname-routing Worker. Each has its own static
|
||||||
|
assets deployment and Cloudflare deployment history.
|
||||||
|
|
||||||
|
## Deployment boundary evidence
|
||||||
|
|
||||||
|
| Evidence | Result |
|
||||||
|
| --- | --- |
|
||||||
|
| Runs 133 and 134 | Shared deployment-workflow change produced one successful blog deployment and one successful primary deployment. |
|
||||||
|
| Commit `4e2d0f8`, run 135 | A change limited to `sites/blog/site.json` produced one successful blog deployment and no primary deployment. |
|
||||||
|
| Public checks | Blog returned 200 with the expected title; its unknown route returned 404. |
|
||||||
|
|
||||||
|
## Operating notes
|
||||||
|
|
||||||
|
The blog is intentionally using the pilot preview build, so its page metadata
|
||||||
|
and generated robots rules are non-indexable until a separately approved blog
|
||||||
|
production release is created. Markdown content collections, CMS integration,
|
||||||
|
and client editing are not part of this phase.
|
||||||
|
|
||||||
|
Rollback one site by selecting a prior deployment in that Worker’s individual
|
||||||
|
Cloudflare deployment history. Do not alter the other Worker or either site’s
|
||||||
|
domain binding during that operation.
|
||||||
Reference in New Issue
Block a user