Hey Ricardo, Yes I considered that. I would like to avoid that as much as I can (if I understand this correctly, fastrouter does similar thing to haproxy/nginx which is routing to "backends", right?). The goal is to keep memory as low as possible and by introducing two applications I'll end up with at least two uwsgi/php processes instead of 1.
I showed that case in a wrong way probably. app-A and app-B are the same app. app-B is just one php file I would like to serve it from different location. User has access to app-A, but I don't want to allow him to edit app-B files, so I wanted to put app-B in separate directory outside of his directory (app-A). I don't want to solve this with permissions as well because of current existing system enforce permissions on app-A files making them writeable and this part cannot be changed. Tom 2015-11-09 11:03 GMT+00:00 Riccardo Magliocchetti < [email protected]>: > Hi Tomasz, > > Il 08/11/2015 20:59, Tomasz Czyż ha scritto: > >> Hi, >> >> I would like to serve two applications with uwsgi: >> - application A under /appA (and all subfolders) >> - application B under / (and all subfolders except /appA) >> > [snip] > >> >> Do you have any ideas how I can set up routing (or other options) to serve >> /app-B from a different directory than app-A? >> > > Have you read about the emperor and the fastrouter? > http://uwsgi-docs.readthedocs.org/en/latest/Emperor.html > http://uwsgi-docs.readthedocs.org/en/latest/Fastrouter.html > > It makes the learning path a bit more steep but it would be easier to > manage in the longer time. > > hth > > -- > Riccardo Magliocchetti > @rmistaken > > http://menodizero.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Tomasz Czyż
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
