what's populating these environment vars? is the main supervisord process being started with these set?
On Mon, Oct 17, 2011 at 1:21 PM, Aleksey Sivokon <[email protected]> wrote: > Hello! > > I propose to allow environ vars expansion in option strings. To prevent > supervisord's own expansions from being overridden, environ vars should be > prefixed (for example, with "ENV_"). > For example: > [program:test] > command = %(ENV_FOO_HOME)s/bin/foo --db %(ENV_FOO_DB)s bar > directory = %(ENV_FOO_HOME)s > stdout_logfile = %(ENV_FOO_HOME)s/log/stdout > stderr_logfile = %(ENV_FOO_HOME)s/log/stderr > > This would be a _great_ help in configuring systems. > I've already implemented this feature: > https://github.com/silver-/supervisor/commit/31e7953dab73a98628e072889fbde6375b51db07, > but didn't make pull request yet -- contacted mail list first. > > Best regards, > Aleksey > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users > > _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
