> Roberto De Ioris <roberto@...> writes: >> Now you need to pass the "name of the app" to it using nginx. >> The name of the app is exposed by the SCRIPT_NAME variable, so >> a /command/foo must be passed as: >> >> SCRIPT_NAME /command >> PATH_INFO /foo >> >> Add uwsgi_param SCRIPT_NAME "xxxxx" to both locations and it will start >> working. >> >> One things left: >> >> nginx cannot rewrite PATH_INFO based on SCRIPT_NAME so by default you >> will >> end with: >> >> SCRIPT_NAME /command >> PATH_INFO /command/foo >> >> To fix this add >> >> uwsgi_modifier1 30; >> >> to both location directives in nginx.conf > > Thank you much, this certainly helped figuring out the issue and resolving > it... The result of my findings this kind of situations is now available @ > http://wiki.nginx.org/HttpUwsgiModuleMultipleDynamicApplications > Perhaps, it makes sense to have it linked/copied to somewhere on uWSGI > site as > well. > > _______________________________________________ >
Thanks a lot, it is a funny/elegant configuration, i always forget how the 'set' nginx directive is useful :) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
