W dniu 15.12.2010 11:22, kevin beckford pisze: > spawn a new process :] eg.
Sorry. I lost context regarding the above. >> Personally I think the supervisord is a weak solution. >> Long ago I resigned from it. > > I am curious, what made you feel supervisor was a weak solution? 1. http://pypi.python.org/pypi/supervisor/3.0a9 - is in Python Python is a very nice language, but should not monitor the key processes. It is not super fast, is a memory-intensive and dynamic types often do not make it predictable. IMHO I will not dwell on the weaknesses Supervisord, better tell you why in conjunction with a uWSGI no sense to use it: Features (from http://supervisord.org/introduction.html#features): 2. Simple - Nginx has its own configuration and uWSGI. For what set up another ?! even simple one. 3. Centralized - I have other tools that are already doing it. Besides I do not know whether centralization is so good. I prefer the dispersal and redundancy. 4. Efficient - subprocesses, daemonize, signals is already in uWSGI and Nginx. 5. Extensible - I've never used it. 6. Compatible - nice, but it is not needed to run uWSGI. 7. Proven - I use it over a year ago, maybe two. Often, crashed and caused more problems than observed process. But you can tell me why you want to use it? What are its features do you need? From another site: First, here will help to create a project which will not require continuous observation. Whoever, without jagged nerves on the production starts process and waits for a tip over. Or, open the web-admin-panel and look for example: four processes do not work, I'll have to do something. If Postgresql required Supervisor (or similar) I have not used this database. Secondly, even if uWSGI fall. It is 95% wind error in the application code, or ran out resources, or someone has made some changes. In none of these cases Supervisor will not help. Try to start the process again. Oh, come on out of disk space :/ lets try again. If there are 500 in the code. Supervisor will not help. If uWSGI fall at most Supervisor, notify you. But it will not send SMS. Probably not even an e-mail does not send. At least I do not remember, it can? From long experience I know that there are often problems with the whole host, Supervisor also does not work. Better monitor the process from the outside and with multiple machines simultaneously (web serwer). And when you are notify, you have to open a console. Ah, Supervisor has a memory limit. uWSGI also. These are my experiences in the context of uWSGI. It is certainly a variety of uses for it, but not here. I just do not see its usefulness. > >> Instead, I wrote a script (in Python), which reads a configuration file >> that contains the path to the nginx, uWSGI sockets directory to the list >> of projects and their locations. > > I did similar, my script is called buildout.cfg. ;) We'll see how to develop project uWSGI. It's fairly young and very fast growing. Maybe next year range of these scripts will surf the Web and other tools to facilitate work. Maybe someone is tempted to link (as one application) this with such Nginx or Cherokee and will issue a branch :] -- Łukasz Wróblewski http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe http://www.hostowisko.pl/ - Profesjonalny i tani hosting http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
