On 30/06/2010, at 05:31, Rocky Borg wrote: > The "Advanced Virtual > Hosting" doesn't seem to support handlers for each virtual host at least > with the default setup. All the sites would have the same file structure > i.e. > > /home/site1.com > /home/site2.com > > What would the easiest way for multiple sites to use the same uwsgi > handler in cherokee. Is there a way to do this with advanced virtual > hosting?
The Advanced Virtual Hosting module will build the Document Root of every single request on-the-fly based on the template that you define. If that virtual server using the AVH module has a uWSGI handler (in the default rule, for instance), it will be used by all the virtual server matching that particular AVH-enabled vserver. Request (example.com) -> AVH -> DocumentRoot /var/www/example.com \ Request (foobar.com) -> AVH -> DocumentRoot /var/www/foobar.com --> Source -> uWSCGI Request (whatever.com) -> AVH -> DocumentRoot /var/www/whatever.com / > It just doesn't seem like a separate virtual host with a > separate process of uwsgi would be the best way to go about this. > Especially since this server could eventually have 20-30+ sites of > varying sizes that need to be deployed immediately when needed (can't be > setup by hand). For example is it possible to use dynamic apps in uwsgi > to add each site with advanced virtual hosting? Any help would be > appreciated as I haven't found any documentation that offers a clear > explanation of this. Well, I guess you could write a little dispatcher in Python as some sort of front-end. Since many of your domains would be handled by the same Python app, it should be able to distinguish and route them to its appropriate sub-app. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
