docs: add "source checkout → release images" upgrade path#254
Merged
Conversation
Document the in-place conversion from a `git clone` (`:dev`, badge reads `dev · branch @ commit`) to the published release images, with the exact steps that preserve config.json/.env/onion-keys/data — the procedure used to move pithead-prod onto a release. - operations.md: new "Switching a source checkout to release images" subsection under Updating the stack (backup → overlay bundle → drop the Dockerfiles to flip build→pull → upgrade), plus how to reverse it and a note that upgrade now requires a primary Monero address. - dashboard.md: point the dev-badge explanation at the new recipe. - getting-started.md: point the "build from source" alternative at it. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Spun out of moving pithead-prod onto a release: there was no documented way to convert a
git clone(which builds:devlocally — thedev · branch @ commitbadge) to the published release images. This adds it.operations.md— new Switching a source checkout to release images subsection under Updating the stack:backup -y→ overlay the release bundle →rm -f build/*/Dockerfile(the switch that flips pithead from build to pull) →upgrade. Explains the build-vs-pull mechanism, how to reverse it (git checkout vX.Y.Zrestores the Dockerfiles), and notes thatupgradenow refuses a non-primary Monero address (1.0.3).dashboard.md— the dev-badge explanation now links to the recipe (where someone confused bydev · …actually lands).getting-started.md— the build from source alternative links to it ("changed your mind later?").Docs-only; anchor verified against the new heading; README already cross-links to
operations#updating-the-stack.