Repository navigation
docs(deployment): beta deploys master, production a release tag; montage-dev's production copy - #658
Merged
Merged
Conversation
…n copy Writes down the deploy discipline to work towards push-to-deploy: montage-dev deploys any branch under test, montage-beta deploys master after every merge, production deploys a release tag (vYYYY.MM.DD) on a commit that ran on beta; rollback is the previous tag. The old montage-dev / montage-beta / montage-prod branches were never used for deploys and still query the old database hosts: they are to be archived as tags. Step 4 shows the ref per tool. Documents montage-dev's database: since 2026-10-05 a shuffled copy of production (#652): what was cut, shuffled and reset, what is still real (usernames, coordinators' free text), who may use it and what not to do with it, and the rollback database kept until about 2026-10-19. Co-Authored-By: Claude Opus 5.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.
Documents how Montage is deployed, as a first step towards push-to-deploy, and documents montage-dev's database.
Deploy discipline (
deployment.md, "Multi-environment setup" and "Deploying new changes" step 4):masterafter every merge; production deploys a release tag (vYYYY.MM.DD) on a commit that has run on beta. Rolling back production is a deploy of the previous tag.montage-dev,montage-betaandmontage-prodbranches were never used for deploys and still query the old database hosts. They are to be archived asarchive/<branch>-<date>tags and deleted.montage-dev's database: since 2026-10-05 a shuffled copy of production (#652): what was cut, shuffled and reset, what is still real (usernames, coordinators' free text), who may use it and what not to do with it, and the rollback database kept until about 2026-10-19.
Note: #656 also edits "Deploying new changes" (it adds a step for required settings); whichever merges second needs a small conflict fix.
Prepared with Claude (Claude Code) on behalf of @lgelauff.