forked from pool/uwsgi
ec165171f5
Web application container server that speaks it's own uwsgi protocol in addition to HTTP. Mainly used in conjunction with Nginx and Python, but supports other servers and languages as well. OBS-URL: https://build.opensuse.org/request/show/133532 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/uwsgi?expand=0&rev=1 |
||
---|---|---|
.gitattributes | ||
.gitignore | ||
django.ini.example | ||
opensuse.ini.in | ||
rails.yml.example | ||
README.openSUSE | ||
trac.ini.example | ||
uwsgi-1.2.6-plugin_build_path.patch | ||
uwsgi-1.2.6.tar.gz | ||
uwsgi.changes | ||
uwsgi.init | ||
uwsgi.spec | ||
werkzeug.xml.example |
==================== openSUSE uWSGI Notes ==================== Emperor Mode ------------ The included init script runs uWSGI in Emperor mode. It will monitor the /etc/uwsgi/vassals directory for configurations and will automatically load and restart uWSGI processes when configuration files are placed there or modified. Some example configurations are provided in the directory. To enable one, rename it without the .example at the end and edit for your application. For more information on Emperor mode, see http://projects.unbit.it/uwsgi/wiki/Emperor Plugins ------- This uWSGI package is fully modular. Some plugins, such as the Python plugin, are not embedded in the main server binary. This means that your application configurations need to specify the plugins it uses. For example, a Python application will need the following option specified: plugins = python Alternatively, uWSGI has a autoload option that will load any plugins when it encounters options for those plugins in the configuration. To enable that, use the following in the configuration: autoload = 1