-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve configuration management for multiple servers #283
Conversation
Allows to use multiple JSON config files that will be merged into a single configuration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need vetting with multiple live servers before it is approved. Also need an answer on the code comment.
|
||
config.json | ||
config.*.json | ||
!config.example.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this excluded?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
config.json
and config.*.json
exclude customized configurations.
config.example.json
is the auto generated configuration example (formerly config.json
) and explicitly included because it matches config.*.json
.
Rather than defining what configs to layer when you run squadjs. I think it would be better to have an include directive (eg |
Review stalled moving this over to #320 CLOSING DUE TO LACK OF RESPONSE |
This allows you to split up your configuration and reuse parts on multiple servers.
This changes the example configuration name as proposed in #275
closes #282, closes #275