> On Fri, Dec 12, 2014 at 6:56 AM, Roberto De Ioris <[email protected]> > wrote: >> >> Hi, the perl/psgi plugin now exposes the uwsgi::opt hashref that >> contains >> all the options set in the current instance: >> >> $VAR1 = { >> 'logdate' => '%d', >> 'master' => 1, >> 'psgi' => 'foo.pl', >> 'http-socket' => [ >> ':9090', >> ':9091', >> ':9092' >> ], >> 'socket' => [ >> ':3034', >> ':3035' >> ], >> 'processes' => '2' >> }; >> >> The patch has been applied to both master and uwsgi-2.0 (will be in >> 2.0.9) >> >> https://github.com/unbit/uwsgi/commit/b59294db89c477d04624fa344c8b9b15435bebd0 > > Very nice, the documentation[1] mentions that "This feature can be > (ab)used to reduce the number of configuration files required by your > application.". Does that mean you can also set configuration through > this feature, or just that you can use uWSGI's config to set options > unrelated to uWSGI itself? > > http://uwsgi-docs.readthedocs.org/en/latest/Configuration.html > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
Unfortunately the second one :) During 1.9 development cycle we introduced 'pluggable configurators': http://uwsgi-docs.readthedocs.org/en/latest/Changelog-1.9.3.html#pluggable-configuration-system-with-lua-support but i think for a perl user piping the config (generated by a perl script) to uwsgi STDIN is more natural :) perl foobar.pl | uwsgi --ini - -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
