[WJ-994] Fix deepwell build in Docker #1894
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
Instead of weird glibc images. Also update dependencies.
Have it reset the db on each new instance, so we need auto-migrate and seeder.
This reverts commit 9f53462.
Hopefully to get the magic database in there.
And get rid of Postgres (add Framerail).
Yossipossi1
approved these changes
Apr 25, 2024
|
thanks @Yossipossi1! |
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.
There were some glibc issues when trying to push the existing deepwell build, instead of bothering with the glibc/musl nonsense we can just use musl by building in the Rust Alpine image instead.
I have pushed the modified image to dev. This PR also adds changes to have it run there, like the environment-specific configuration files.
While working on this, I also added dev Dokku deploys for the "push" GitHub workflow files.