For this purpose, I use virtualenvwrapper. You can then put everything into your postactivate file (in /bin) and it will be run automatically.
-- Sent from my phone On 24 Oct 2012, at 19:44, Jonathan Vanasco <[email protected]> wrote: > For staging/production, I tend to write startup scripts per machine. > For a while i was doing shell scripts, but then I started using > Fabric. > > For local development, i have a 'source' file , that typically does > this: > > 1. cd path_to_pyramidapp > 2. source path_to_virtualenv/bin/activate > 3. handle any variables > > whenever i need to start working on a project: > > $ source go_myapp.source > > and then i'm in the right directory, with the right virtualenv, and > all the right env vars > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
