Organizing your Python environments¶
When your server is going to host several production sites, then it is likely
that every project wants its own virtualenv.
You will create a new virtualenv for every project and store it below
the project directory. We recommend to always use the same name, e.g.
By convention, on a production server hosting several projects, every
project directory has a subdirectory
env which contains the
Python environment used by that project.
Such a convention allows you for example to create an alias command
like the following in your
alias a='. env/bin/activate'
This alias is also installed by getlino.