heckyel/mediagoblin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Note on what --without-virtualenv does

Browse Source
This commit is contained in:
Christopher Allan Webber 2015-04-28 14:14:44 -05:00
parent fd4ddeb14e
commit 8d59cd1f98
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/source/siteadmin/deploying.rst
View File

@ -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 you're familiar with Python packaging you may consider deploying with
your preferred method. 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 Assuming you are going to deploy with FastCGI, you should also install
flup:: flup::