honcho[1] might be a good fit. It's Python, supports an environment file, and will supervise all your processes.
[1] https://github.com/nickstenning/honcho On Wed, Dec 30, 2015, 11:19 Iain Duncan <iainduncanli...@gmail.com> wrote: > Hi everyone, we've got a distributed system in the works with a handful of > python process, some are pyramid apps, some are just worker processes > waiting on queues. In order not to have multiple config files, I have all > my config settings for everything in one file of env vars that doesn't go > in git but does get sourced before anything is turned on. I'm trying to > figure out which supervisor to use that will make this easies, ideally it > would be nice if I could tell the supervisor to source a file or import a > whole bunch of env vars (more than is convenient to put in the supervisor > config file). Maybe I need to just use a shell script. Anyone have opinions > on this one? > > thanks! > iain > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-discuss@googlegroups.com. > Visit this group at https://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
