> 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
