On 27 November 2013 10:45, Roberto De Ioris <[email protected]> wrote:
> > do not do that: UWSGI_VASSAL_SOCKET=xxx > > > let each vassal have its own <socket> directive. (in your specific case it > cannot even work a magic vars are expanded only in config files) > > For starting the Emperor you only need the --emperor option. > Thanks for a quick reply. I have tried that out of desperation because without it I get the same result - no socket and a *502 Bad Gateway* from nginx. Why do I get *[emperor] removed uwsgi instance web2py.xml?* Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
