>
>
>
>>
>>   Or, options could be passed to started instance "implicitly", as
>> environment variables. So Emperor exports variables
>> UWSGI_PIDFILE=/var/run/uwsgi/cool-site/pid,
>> UWSGI_SOCKET=/var/run/uwsgi/cool-site/socket and
>> UWSGI_LOGTO=/var/log/uwsgi/cool-site.log and starts instance in modified
>> environment with more sane command line '/usr/bin/uwsgi --yaml
>> /etc/uwsgi/cool-site.yml'.
>
>
> I have committed support for UWSGI_VASSAL_ env vars.
>
> They are ignored by the Emperor but translated to the corresponding
> UWSGI_ vars in the instances.
>
> So a UWSGI_VASSAL_THREADS=40 will became UWSGI_THREADS=40.
>
> I have (still) not added support for magic vars (%s, %n ...) as i have
> just added them to ini/xml/yaml parsing. So independently from the Emperor
> you can use the following vars in your config files:
>
> %s the filename of the config file
> %o the original string passed to --xml/--yaml/--ini
> %p the full path of the config file
> %n the filename of the config file without extension
> %e the estension of the config file
>
>
>>
>>   2. Hooks are simple executables (shell scripts or any other scripts or
>> compiled executables) which are invoked in corresponding phase with
>> passing emperor and instance options and configuration file name
>> (without extension) as environment variables.
>>
>
> I will think about it for sure
>
>

An important thing i have forgot to mention:

config files for emperor can be symbolic links, this will open lot
of scenarios for mass hosting.

For example you can have a base.xml config file

<uwsgi>
<chdir>/home/%n/www</chdir>
<socket>/var/sockets/%s.sock</socket>
<module>wsgi_app</module>
<uid>%n</uid>
<gid>%n</gid>
</uwsgi>


Then for every customer/user you want to allow running wsgi apps simply
do:

ln -s base.xml myrichuser.xml

As soon as the user will put a wsgi_app.py file in its home, it will be
started

-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to