docs(landing): fix stale deploy runbook#58
Merged
Conversation
DEPLOY.md pointed at /var/www/loci.garden (does not exist) and said `git pull`, which fails on the VPS checkout due to a rewritten history. Corrects the served-root description (Caddy file_server off landing/), documents fetch + reset --hard, and keeps operator specifics out of the public repo. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <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
landing/DEPLOY.mdwas stale and wrong in two ways that would mislead anyone deploying:/var/www/loci.gardenas the site root. That dir does not exist. Caddy'sfile_serveractually serves thelanding/subdir of a git checkout, straight off disk.git pull. The repo history was rewritten once (filter-repo scrub), so a long-lived VPS checkout has a forked history and will not fast-forward. The doc now documentsfetch+reset --hard origin/mainand explains why.Also removed the
index-old.htmlswap rollback in favour of a dir-copy backup (what's actually used), and kept host/path/credentials out of this public file per outgoing-quarantine discipline.Test plan
root * .../landing) and the actual deploy performed this session