Implement a set subcommand
#6
Labels
Comments
natefoo
added a commit
to natefoo/gravity
that referenced
this issue
Mar 20, 2015
… working,
although no previous state is preserved at this pointi, which will be
necessary to actually update supervisor. Adding/removing configs and
instances is all done via `galaxy create` and `galaxy destroy` now,
e.g.:
% galaxy create foo/bar config/galaxy.ini
`foo` is the instance name
`bar` is the config's "alias", aka a name that can be worked with
Most of everything else not related to adding/removing configs and
setting options is completely broken because the state file data
structure has completely changed and none of those functions have been
updated yet.
|
This is all outdated and irrelevant, Gravity has its own YAML config section now, the idea of cli configuration was dropped. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The initial use case for this was the need for
galaxycfg set instance_name autostart trueto override the current hardcoded default of not starting instances whensupervisordstarts.However, this led me to consider whether it's better to move the file-driven configuration of
[galaxy:server]ingalaxy.iniinto a command line-driven configuration.In favor of putting things in
galaxy.ini, it's a familiar config interface for admins and those settings persist across removal from gravity, and in a location that is expected by the admin. However, the cli config paradigm seems to be fairly popular these days (see: docker, vagrant, zfs), and has the benefit of allowing for rapid changes and instantaneous syntax checking.One downside of the cli-driven configuration is that settings would be persisted to a the internal
configstate.jsonwhich users should not edit by hand. I think people prefer to have the option to config either way - for example, if I was deploying (e.g. with Ansible), I want to be able to write a config file rather than have to call a bunch of shell commands.The text was updated successfully, but these errors were encountered: