cmd/catalyst: implement stack of configuration files#680
Draft
iameli-streams wants to merge 6 commits intolivepeer:mainfrom
Draft
cmd/catalyst: implement stack of configuration files#680iameli-streams wants to merge 6 commits intolivepeer:mainfrom
iameli-streams wants to merge 6 commits intolivepeer:mainfrom
Conversation
a1451da to
283a8af
Compare
283a8af to
6ebd893
Compare
f0d0919 to
6b4a0fe
Compare
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
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.
For overriding stuff! This will allow people to better override configuration settings in their development environment and set up the framework for people to run their own boxes in production-like settings.
I'm trying to figure out the new command-line options and it's hard. Braindump:
It's confusing because there's a few operations here:
exec)roll-mist)Workflow: Boot up a prod server
catalystWorkflow: Boot up a canary server w/ a custom manifest pointing at different branches
catalyst --update-manifest --downloadWorkflow: Download binaries from manifest (Dev environment init)
catalyst --download --exec=falseWorkflow: Build a new manifest (CI)
catalyst --update-manifest --exec=falseWorkflow: Run an inplace-deploy on a prod server (Manifest from somewhere else)
catalyst --download --roll-mist