On Tuesday, November 27, 2012 8:45:56 PM UTC-8, Roy Smith wrote:
> In the future, the plan is to build a complete fresh virtualenv for
> every deployment. But we're not there yet.
Maybe a repository of virtualenvs, then when deploying you can see if there's
one the matches what you need and use
In article ,
Miki Tebeka wrote:
> > When we deploy, we create a new virtualenv, then do
> > "pip install -r requirements.txt".
> 1. Do you do that for every run?
Well, sort of.
We are currently using a single virtualenv per deployment host. Each
time we deploy new code, we checkout all th
On Tuesday, November 27, 2012 8:21:48 PM UTC-8, Roy Smith wrote:
> What we do is run "pip freeze > requirements.txt" and check that into
> version control.
That's the idea I was toying with, thanks for confirming.
> When we deploy, we create a new virtualenv, then do
> "pip install -r requirem
In article <8ea52e1b-2e02-40b2-8ce0-fcce7fc2e...@googlegroups.com>,
Miki Tebeka wrote:
> Greetings,
>
> The usual package mangers (easy_install, pip ...) install packages in one
> central location.
>
> I'm looking for a solution that will allow every project (which run on the
> same machine)
Greetings,
The usual package mangers (easy_install, pip ...) install packages in one
central location.
I'm looking for a solution that will allow every project (which run on the same
machine) use it's own packages and versions of packages. (Context - we're
running several applications on the s
