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. Otherwise it doesn't matter where the `uwsgi` binary is -- /usr/local/bin or /opt/bin, depending on your preferences, are popular choices.
But on principle I do agree with your "not mixing packages with manually compiled binaries" sentiment -- 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) :) /A -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gilles Sent: Wednesday, May 15, 2013 12:32 PM To: [email protected] Subject: Re: [uWSGI] [nginx 0.8.40+] Configuring uWSGI? On Tue, 14 May 2013 22:53:00 -0500, C Anthony Risinger <[email protected]> wrote: >maybe not helpful, but methinks you're making it more complicated than >necessary... Thanks for the input. It's just that I don't like mixing packages and manually-compiled applications because packages make it easier to keep a system up-to-date. But I don't mind going the manual way to experiment. BTW, since uWSGI is a stand-alone binary application, I don't understand how it fits with virtualenv: Does it mean I should copy uWSGI into the directory created by virtualenv? _______________________________________________ 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
