♻️ Simplify Docker Compose deployment - #2435
Merged
Merged
Conversation
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
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.
♻️ Simplify Docker Compose deployment
Before
Before this PR it would assume (and require) a staging and production servers and deployments, and two environments in GitHub, which are not available in private repos using GitHub free. So it would have a strong requirement on a paid GitHub plan.
It would deploy to staging on merge/push to the main branch, and then to prod only when making a GitHub release.
This PR
This PR simplifies all that assuming a single production environment, and deploying on push/merge to the main branch.
From this simpler baseline developers will be able to extend to any environments they might need, staging or more, and any other release/deployment strategy.
AI Disclaimer
Using Codex with gpt-5.6-sol. Reviewed manually.