Feature/dockerized#276
Merged
Merged
Conversation
added 7 commits
September 9, 2017 18:57
Owner
|
Love this - thanks for the PR! Will be pulling this in with the slack release. |
Owner
|
Actually, going to pull this in to 1.0.1, since the config is so different for 2, and it's packaged up and documented so well. Thanks for this, @Mike-love ! |
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
2 participants
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.
Adds support for containerized deploy, pulled from pip. Leverage's redis as the db.
Noticed #269 I did this for our production deployment at my co; it's not pushed to docker public repo but very easily could be tagged and shipped up to docker reg as part of the CI/CD.
That's how I have built ours, publishes to an internal docker registry, which is then pushed down to the instance and the containers restart.