fix: revert how we initiate mongo database in docker-compose local dev #3541
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
since we've rolled back to v5, this is unneeded and causes fresh builds to fail First introduced in #3039
keep consistent with the database version we are using in prod
timotheeg
reviewed
Mar 3, 2022
timotheeg
approved these changes
Mar 3, 2022
Merged
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.
Since we've rolled back to v5 in #3219, this is unneeded and actually causes fresh builds to fail.
First introduced in #3039
Also update the mongo image we use in docker-compose to 4.2 to achieve consistent with production version