On Tue, Mar 25, 2008 at 1:34 AM, Roger Hoover <[EMAIL PROTECTED]> wrote: > Another option is to use a template engine such as Perl Template Toolkit or > Cheetah to expand environment variables first and generate your supervisord > config file.
That pretty much the path I have taken. What I also found is that adding environment variables to the command value also do not get replaced, unlike how it would if you were to run the command straight of the shell. For e.g. command=this_is_my_command $USER If you were to run that off the shell directly the $USER variable gets replaced. This does not happen when run through supervisord. YOu end up with the literal $USER being passed to the command. Or am I missing something ? <snip> Mohan _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
