docs: add local→test→prod deploy-cycle runbook
Distills the 2026-07 Grav 2.0.4→2.0.7 cutover into a repeatable procedure: the three-layer state model (plugin code / repo config / host env tree), ordered per-phase make-target sequences, a smoke checklist that catches the code-vs-config, stale-version, garbage-page, and git-sync-boomerang gotchas, plus rollback and one-line invariants. Linked from CLAUDE.md Remote operations. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Np4cMQLF77i664CAQXySzU
This commit is contained in:
@@ -134,6 +134,8 @@ After updating, also create the new trip's page tree under `user/pages/01.trips/
|
||||
|
||||
Always use `make` commands for anything on the production server (`make remote-install-plugins`, `make remote-clean`, etc.) — never SSH directly since credentials live in `.env`. If a remote operation isn't covered by an existing `make` command, either ask the user to run it manually or suggest adding a new `make` command if it seems reusable.
|
||||
|
||||
For a full upgrade/deploy through local → test → prod (ordered steps, smoke checklist, rollback), follow the runbook at [`docs/guides/deploy-cycle.md`](docs/guides/deploy-cycle.md).
|
||||
|
||||
### Content sync
|
||||
|
||||
- `make content-push` — commit and push `user/` to Gitea (triggers production pull via webhook)
|
||||
|
||||
Reference in New Issue
Block a user