Yes! I want a fastrouter speaking fastcgi. Is it possible?
------------------------------------------------------------------------------------ I tried an alternative hack, wrap another uWSGI server around it by using Internal routing: uwsgi --fastcgi-socket :9000 --route ".* uwsgi:127.0.0.1:6999,0,0" :6999 is the fastrouter. But connecting to fastcgi at :9000 still fails > --- no python application found, check your startup logs for errors --- If we run http-socket instead uwsgi --http-socket :8080 --route ".* uwsgi:127.0.0.1:6999,0,0" it totally works. I wonder if fastcgi-socket is second citizen compared to http-socket? On Fri, Dec 30, 2016 at 5:06 PM, Roberto De Ioris <[email protected]> wrote: > > > The doc says > > > > http://uwsgi-docs.readthedocs.io/en/latest/SubscriptionServer.html > > > >> The subscription system is currently available for cluster joining (when > > multicast/broadcast is not available), the Fastrouter, the > HTTP/HTTPS/SPDY > > router, the rawrouter and the sslrouter. > > > > In 2.0 only uwsgi->uwsgi and http/https->uwsgi combos are supported. > > In 2.1 http/https->http is supported to. > > If i understand correctly you want a fastrouter speaking fastcgi instead > of uwsgi, am i right ? > > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
