You might want to do "exec ./start-foo.py", which will replace the current process with the Python process. Then you won't need the pidproxy stuff.
Supervisor2 also now has an environment-setting configuration value; if you use this, you can activate the environment just by setting PYTHONPATH appropriately.
Yep, that's a nice improvement.
You also need to be careful to make sure that cherrypy's autoreload stuff is disabled (using server.environment="production" is good enough) or you get multiple python processes running and again, supervisord can't properly send them signals.
Ian Bicking - 2006-09-13 20:08:08
You might want to do "exec ./start-foo.py", which will replace the current process with the Python process. Then you won't need the pidproxy stuff. Supervisor2 also now has an environment-setting configuration value; if you use this, you can activate the environment just by setting PYTHONPATH appropriately.anders pearson - Wed 20 Sep 2006 14:31:30
Yep, that's a nice improvement. You also need to be careful to make sure that cherrypy's autoreload stuff is disabled (using server.environment="production" is good enough) or you get multiple python processes running and again, supervisord can't properly send them signals.