> On Mon, 15 Apr 2013 18:13:43 +0200, "Roberto De Ioris" > <[email protected]> wrote: >>> --http is added by the http plugin (requiring the corerouter plugin) >>> >>> Just compile both (and load the 'http' one as you load python) >>> >> >>oh, and as you are on an embedded system with few resources, use >>--http-socket instead of --http to avoid an additional process > > Sorry, I'm new to uWSGI. Do you mean doing this? > > 1. UWSGI_PROFILE=core make > > 2. Run this once: > > python uwsgiconfig.py --plugin plugins/python core > python uwsgiconfig.py --plugin plugins/http core > > 3. From then on, uWSGI must always be configured/run with > "--plugin=python", eg. > > uwsgi ----http-socket :9090 --plugin=python --wsgi-file foobar.py > >
The vast majority of uWSGI features are implemented as plugins: https://github.com/unbit/uwsgi/tree/master/plugins each one can be embedded in the server binary or dynamically loaded. Generally, distro supplied packages are fully modular, this is good for reducing memory usage and for avoiding having dozens of different binaries. You can build a tiny binary + the python plugin (as you have already done). The --http option is exposed by the http plugin, it offers an http/https/spdy proxy to put in-front of your apps. As you are on a tiny system, having a proxy could be useless so you can start your instance in pure http-mode (via the --http-socket that is part of the server core, not a plugin) So --http != --http-socket the first one is implemented by a plugin, the second one is part of the server core. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
