Here it is the modification I have done : https://bitbucket.org/yml/uwsgi-emperor-template-configuration/src
So my plan is to have multiple virtualenv in this directory structure. One called "uwsgi-tip" that would be a sibling of vassal-sites, it will be used by the emperor/router instance. Then I would like to have a virtualenv per vassal-sites: site1/ve, site2/ve I use this shell script call start-uwsgi.sh to start the emperor/fastrouter uwsgi instance. I see this in the log file: -------------8<------------ [uWSGI] parsing config file ./vassal-sites/site2/site2.xml *** Starting uWSGI 0.9.7-dev (64bit) on [Thu Feb 3 00:17:01 2011] *** compiled with version: 4.4.3 writing pidfile to ./uwsgi.pid my PID is 7489 chdir(): No such file or directory [uwsgi.c line 871] -------------8<------------ I assume that the issue is this directive : <chdir>%p%s</chdir> It seems that the "%p%s" doesn't get substituted. Could you please be kind enough to point me the problem and let me know how to fix it. Thanks Regards, --yml On Wed, Feb 2, 2011 at 11:06 PM, Yann Malet <[email protected]> wrote: > Roberto, > I am going to give it a try and update my bitbucket toy project until I get > the complete example working. > Thanks > Regards, > --yml > > > On Wed, Feb 2, 2011 at 4:47 PM, Roberto De Ioris <[email protected]> wrote: > >> >> > Roberto, >> > >> > This sounds amazing, I have to say that I read your mail several times >> > today >> > trying to understand everything :-) There is a lot of thing there. It >> > sounds like soon we will have a simple solution to deploy multiple sites >> > on >> > a server without having to modify a zillion files. >> > >> > I like this graph very much : >> > >> > client -> webserver -> uwsgi emperor (router) -> uwsgi vassal -> client >> > >> > If I understand this correctly it means that we will not have to modify >> > the >> > webserver configuration each time we add a new vassal site. The only >> > operation required would be to drop the appropriate uwsgi config in the >> > vassal site and eventually add a line in the router configuration. >> > >> > In my original example the vassal site directory will probably be the >> > "SERVER_NAME:SERVER_PORT": >> > * example1.com >> > * example1.com:8081 >> > * example2.com >> > >> > Thank you for following this discussion. >> > >> > I am looking forward reading and testing your proposal. >> > >> > Regards, >> > --yml >> > >> > >> >> >> Ok, just committed a heavy stone :) >> >> 1) Now the emperor can take a "glob" path, so you can do something like >> this >> >> uwsgi --emperor "/etc/uwsgi/vassals/xx*/*/*.xml" >> >> 2) Added (as promised) the uwsgi fastrouter plugin. >> I can say only one thing: i am totally surprised (and proud) of the >> performance of the new async stack. The fastrouter has pratically >> no-impact >> even on more than 100 different instances (and more of 10000 concurrent >> connections) running on the same system via unix socket. >> >> I will write a post about how to use/configure it in the next few minutes >> -- >> Roberto De Ioris >> http://unbit.it >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
