From: Christopher Allan Webber Date: Tue, 28 Apr 2015 19:14:44 +0000 (-0500) Subject: Note on what --without-virtualenv does X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=8d59cd1f9884dcad94c9810e48317471d0b27d71;p=mediagoblin.git Note on what --without-virtualenv does --- diff --git a/docs/source/siteadmin/deploying.rst b/docs/source/siteadmin/deploying.rst index c7b06be0..74ef1f86 100644 --- a/docs/source/siteadmin/deploying.rst +++ b/docs/source/siteadmin/deploying.rst @@ -238,6 +238,24 @@ more reliable and considerably easier to configure and illustrate. If you're familiar with Python packaging you may consider deploying with your preferred method. +.. note:: + + What if you don't want an in-package ``virtualenv``? Maybe you + have your own ``virtualenv``, or you are building a MediaGoblin + package for a distribution. There's no need necessarily for the + virtualenv produced by ``./configure && make`` by default other + than attempting to simplify work for developers and people + deploying by hiding all the virtualenv and bower complexity. + + If you want to install all of MediaGoblin's libraries + independently, that's totally fine! You can pass the flag + ``--without-virtualenv`` which will skip this step. + But you will need to install all those libraries manually and make + sure they are on your ``PYTHONPATH`` yourself! (You can still use + ``python setup.py develop`` to install some of those libraries, + but note that no ``./bin/python`` will be set up for you via this + method, since no virtualenv is set up for you!) + Assuming you are going to deploy with FastCGI, you should also install flup::