Yes, they are unchanged as far as I have tested. We have a few projects that use virtualenv with webware and those projects require nothing additional from the webserver configuration beyond any additional environment variables you might need - though you probably know about those.
Is this a dev/staging server? I wouldn't recommend using virtualenv in production. I've been burnt personally by virtualenv, but maybe I'm just missing some configuration to control package versions better. Now what I do is use a 15 line bash script to make a tarball of the packages as installed on a dev box by virtualenv and distribute the tarball. With that technique I can know whether the specific versions of everything deployed on a production server were tested thoroughly. I also have better control over sys.path. Ryan On Fri, Mar 6, 2009 at 7:30 AM, kevin <[email protected]> wrote: > > > On Mar 6, 5:15 am, Alvaro Lopez Ortega <[email protected]> wrote: >> On 06-mar-09, at 14:01, kevin wrote: >> >> > What steps are necessary to run a django project out of a virtualenv >> > under cherokee? >> >> http://www.cherokee-project.com/doc/cookbook_django.html > > Right, read that. So these steps are unchanged if i am running my > code out of a virtualenv sandbox then? > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
