Skip to content
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

supervisorctl read from ~/.supervisorctl.conf #528

Closed

Conversation

msabramo
Copy link
Contributor

@msabramo msabramo commented Dec 2, 2014

This is a good place for users to do user-specific customizations, like change the prompt or add plug-ins.

This is a good place for users to do user-specific customizations, like
change the prompt or add plug-ins.
@msabramo
Copy link
Contributor Author

msabramo commented Dec 2, 2014

or to add color to supervisorctl status output which is a PR that I hope to submit soon... 😄

[supervisorctl]
colorize_status = True

@msabramo
Copy link
Contributor Author

msabramo commented Dec 3, 2014

@mcdonc: What do you think?

@msabramo
Copy link
Contributor Author

msabramo commented Dec 4, 2014

Here's the colorized status PR that I alluded to above: #530

@WhyNotHugo
Copy link

I'd rather follow the xdg-basedir-spec and read per-user settings from $XDG_CONFIG_DIR/supervisord/supervisorctl.conf (~/.config/supervisord/supervisorctl.conf by default) I actually had a similar patch in mind for supervisord in mind as well already.

@mnaberez
Copy link
Member

I've left some comments about the search paths over in #576. I would welcome discussion about this and other search path issues in that thread.

@mnaberez
Copy link
Member

I'm going to close this in favor of #742. Several people now have requested letting the config filename be set by an environment variable so I've come around on it. If that was implemented, this PR would not be needed, since you could put export SUPERVISOR_CONF=$HOME/supervisord.conf in your ~/.profile.

@mnaberez mnaberez closed this Jul 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants