PoC: Tweak local infrastructure to ease switching branches #5711
Conversation
This file contains 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.
This is a change to the local-development setup.
It will create a "per-branch" environment using Docker.
So the biggest change in workflow would be that you'd need to explicitly "stop" any environment your currently work in BEFORE switching/creating another git-branch.
Breaking changes
the "121-redis"-container is renamed to "121queue", so any references to it in your local
services/.env-file need to be changed (see.env.example.Also use of the ENV-variable:
COMPOSE_PROJECT_NAMEis no longer necessary.Any other comments? Let me know!
Checklist before requesting a review