Infra: docker-compose repository #556
Merged
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
|
I'm still getting the error |
|
@psschwei with profile |
|
full |
|
This seems to be the error (from the compose logs): |
? |
|
ok, looks like I may have been caching things... deleting and recreating got it working |
psschwei
approved these changes
May 16, 2023
|
Tomorrow we will create proper fix :) |
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.
Summary
Hotfix for local docker-compose setup.
Details and comments
Gateway and repository has the same application name and same table programs. Therefore migrations in both applications were creating the same table in the same database. Migration passed as it was thinking that those table existed already.
This PR is a hotfix to make docker-compose with
full,defaultandjupyterprofile work.Real fix will be implemented within #555
Closes #552