> I'm not sure if this is a good idea in the least, but it just occurred to > me and it might just work: > > For each deferred vassal config file, have a secondary file for the socket > containing just the > activation socket spec: > > /etc/uwsgi/vassals/awesome-app.ini > [uwsgi] > blah = blahblah > > /etc/uwsgi/vassals/awesome-app.ini.socket-def (not .sock to disambiguate > from UNIX sockets) > 127.0.0.1:8080 > > /etc/uwsgi/vassals/i-like-xml.xml > <uwsgi>...</uwsgi> > > /etc/uwsgi/vassals/i-like-xml.xml.socket-def > /run/sock/xml-is-awesome.sock > > etc. > > - Aarni
Hmm, you know, it seems the most easy and handy way. Basically we just need to tell the emperor to look for a specific extension (.socket-def in your case) before spawning a vassal. If it exists its content will be used as a socket (otherwise normal spawning will continue). This will retain backward compatibility and will require tiny modification to the code. It could be not very "elegant", but who cares :P +1 for me -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
