How to get through¶
There are some many options, how to start?
Start with a preset configuration. For example, if you have a Python web-app try out
Basic things to do are: define
wsgi_module and do
This should already give a more or less decent decent configuration.
After that you can skim through option groups (such as
and deep into uWSGI abilities.
Use from virtualenv¶
I have a virtualenv in venv/ directory (where I have uWSGI and uwsgiconf) and configuration module outside of it, how do I run it?
You can try the following trick (from directory containing
$ venv/bin/uwsgiconf run
Unknown config directive¶
PythonSection for configuration and get [strict-mode] unknown config directive: wsgi-file on start. What’s that?
uwsgiconf enables configuration options check (aka
strict-mode) by default.
If uWSGI plugin which provides some options is not available, you’ll get the message. That’s because
by default won’t instruct uWSGI to load Python plugin (since if you get uWSGI from PyPI you already have
Python and a bunch of other plugins embedded, so there’s no need to load them).
If you get that message most probably uWSGI is provided by your OS distribution (e.g. on Debian you’ll need to install plugin packages separately from uWSGI itself).
In that case you can try to set
PythonSection (see Quickstart example).
Another option is to quickly fire up
uWSGI to check what plugins are embedded (the same can be achieved with
$ uwsgiconf probe_plugins command).
uwsgiconf can also do it for you automatically on configuration stage:
Using the above,
embedded_plugins will be inhabited by plugins actually available in uWSGI.