chore(deploy): PR-4 - env templates, systemd units, nginx blocks, DEPLOY.md - #4
Merged
Merged
Conversation
…— three storefronts one box
Phase 0's last rung: everything the VPS needs to serve all three domains
from one checkout.
- deploy/{orlando,national,directory}.env — EnvironmentFile templates
(REPLACE_ME placeholders; never real tokens in git)
- deploy/systemd/salon-{orlando,national,directory}.service — one unit per
storefront, journald logging, on-failure restarts; blast radius stays
per-process
- deploy/nginx/salon-platform.conf — three server blocks, port 80 behind
Cloudflare per locked TLS decision 4 (Flexible now, Full Strict queued
with 443 blocks when flipped); installed via Mail-in-a-Box's custom
config hook, never raw sites-enabled
- DEPLOY.md — first deploy, verify (health + robots + sitemap per port),
update, rollback (git revert for code, engine AS OF for content)
No app code changed; CI (typecheck/unit/live matrix/audit/build) is the
regression proof. Real validation is the first VPS deploy — stated
plainly in DEPLOY.md's verify section rather than claimed here.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR-4 closes Phase 0: the deploy artifacts. Env templates, systemd units, nginx server blocks, and a DEPLOY.md that takes the VPS from clone → three live storefronts with a verify section at every step.
Why this matters
Phase 0's exit test was "three domains serving distinct branded shells from one commit." The code has proven it in CI since PR-2; this PR makes it executable on the box:
npm run buildonce, three units, three server blocks, one shared engine.What's inside
deploy/*.env— per-campaign EnvironmentFile templates (REPLACE_MEplaceholders — real tokens never touch git)deploy/systemd/salon-*.service— one unit per storefront; journald carries the campaign-tagged request log; per-process blast radiusdeploy/nginx/salon-platform.conf— three port-80 server blocks behind Cloudflare, Flexible TLS per locked decision 4 (Full Strict queued — 443 blocks slot in when flipped); installed via Mail-in-a-Box's custom hookDEPLOY.md— first deploy, verify, update, rollback (git revert for code; engineAS OFfor content)Tests run
No app code changed — CI's full gauntlet (typecheck · unit 18 · live matrix · audit · build) ran green on this PR as the regression proof. The deploy artifacts themselves are validated by the first real VPS deploy, not claimed green here — DEPLOY.md's verify section is that checklist.
Follow-up work
Spec: §12 (deployment), §15 (roadmap PR-4). Phase 0 complete on merge.