On Tue, Feb 19, 2013 at 7:59 PM, Roberto De Ioris <[email protected]> wrote: > >> On Tue, Feb 19, 2013 at 7:24 PM, Roberto De Ioris <[email protected]> >> wrote: >>> >>>> On Tue, Feb 19, 2013 at 5:10 PM, Roberto De Ioris <[email protected]> >>>> wrote: >>>>>> hi all, >>>>>> i'd like to use uwsgi's emperor mode for shared hosting, mainly >>>>>> serving php, cgi, static files. so far i have managed to set up >>>>>> emperor mode with one vassal per domain, but my goal is to have one >>>>>> vassal for every customer regardless of how many domains the customer >>>>>> has, i want to assign him e.g. a vassal with 5 worker processes which >>>>>> should be shared to serve all his domains. is that possible in uwsgi? >>>>>> i have only found in the docs >>>>>> http://projects.unbit.it/uwsgi/wiki/VirtualHosting but that is about >>>>>> serving python webapps, not cgi/php/static and with different >>>>>> document >>>>>> roots for each domain. thanks. >>>>>> _______________________________________________ >>>>>> >>>>> >>>>> Hi, if your frontend-webserver correctly set the DOCUMENT_ROOT >>>>> variable >>>>> you should be able to use php, cgi and static file serving for >>>>> multiple >>>>> domains without problems. >>>>> >>>>> For static files add check-static-docroot = true (this will serve >>>>> static >>>>> files from the passed DOCUMENT_ROOT) >>>>> >>>>> For php you do not need special options. If you want to increase >>>>> security >>>>> just use php-allowed-docroot >>>>> >>>>> for cgi use cgi-from-docroot that works in a way similar to >>>>> check-static-docroot. >>>>> >>>>> Remember to set the allowed extensions you want to use for php script >>>>> and >>>>> CGIs >>>> >>>> thank you, that works well. i have one more question now, is it >>>> possible to use mount and route only for certain domains? e.g. a >>>> customer has domain1.com, domain2.com, domain3.com but only wants to >>>> use mount a webapp or protect a directory with basicauth on one but >>>> not all of them. >>>> _______________________________________________ >>>> uWSGI mailing list >>>> [email protected] >>>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >>>> >>> >>> I suppose you want to give users the same features they can use with >>> .htaccess. In 1.9 they will be able to do lot more, i think i will write >>> updated docs in the week end. But yes, they can make routing >>> configuration >>> per-domain >> >> yes, we want go from apache2+suexec+suphp to nginx+uwsgi, we must >> replace mod_rewrite which is often used in .htaccess. >> so with the uwsgi release it is not possible to have route/mount for >> one domain only if i want to use one vassal for several domains? >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > > It is more or less possible even with 1.4 but the config is really complex > and redundant (and prone to errors). Honestly if your users are used to > .htaccess they could find too much limits in 1.4 implementation, while > with 1.9 they could even manage rules in one file per-domain
ok. I'm still interested to see how it works in the 1.4 release, would you mind posting it nevertheless? _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
