By the way -- just as an experiment, with Vagrant (http://vagrantup.com) it takes all of this much to set up uWSGI (latest released version, 1.9.10 at the time of writing) on a brand new VM.
(host)$ vagrant init precise64 http://files.vagrantup.com/precise64.box (host)$ vagrant up (host)$ vagrant ssh (vm)$ sudo apt-get install -y python-dev python-pip build-essential (vm)$ sudo pip install uwsgi (vm)$ # toy around with /usr/local/bin/uwsgi So that's sort of cool. :) Aarni -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Aarni Koskela Sent: Wednesday, May 15, 2013 3:55 PM To: uWSGI developers and users list Subject: Re: [uWSGI] [nginx 0.8.40+] Configuring uWSGI? It's really about Debian's (imho too) strict policy regarding package versions and freezing them to avoid regressions. This has, incidentally, been under debate in the Debian community as of late. It's also a matter of uWSGI's development being, let's say, spectacularly fast at times (https://github.com/unbit/uwsgi/tags for proof), with the occasional corner case regression happening, so it'd be hard to fit into/justify wrt Debian's release model. However it's not a matter of non-x86 discrimination :) If you check http://packages.debian.org/search?keywords=uwsgi you'll find that it's the same old version (1.2.3 -- I believe that's old LTS) for all platforms. I believe this is Debian policy too. But anyway, with building uWSGI from source being as easy as it is, it's pretty trivial to try new versions of the server at the drop of a hat (and you can even do that while still processing requests, only upgrading some workers at a time, if that's what you fancy). The only place where I can imagine this being a pain in the ass is a larger platform upgrade that may or may not break library ABIs your hand-compiled uwsgi relies on... but even then, a simple 1-minute re-build of the server should get you back up and running. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gilles Sent: Wednesday, May 15, 2013 3:19 PM To: [email protected] Subject: Re: [uWSGI] [nginx 0.8.40+] Configuring uWSGI? On Wed, 15 May 2013 09:48:36 +0000, Aarni Koskela <[email protected]> wrote: >When you install uwsgi using `pip install uwsgi` within an activated virtualenv >(or use `venv/bin/pip install uwsgi`), it will be installed within that >virtualenv's bin/ directory and will thus be available in PATH >(see `which uwsgi`) when that venv is active. Thanks for the clarification. > it _would_ be mighty nice to have an alternate repo >for fresh (LTS/stable/testing) statically-compiled, >no-pathological-plugin-madness uWSGI packages for Debian (and Ubuntu) :) Out of curiosity, is the fact that only older uWSGI packages are available because uWSGI just isn't used much on non-x86 hosts? _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
