Thanks for your answer. I agree with you. For staging/production, fabric is the way to go, even though I haven't taken time to learn it properly yet.
For development, ....our team is really young and new to Python, linux for that matter. I'm in China, everyone uses Windows here. I wanted a one step solution such that it doesn't change their workflow as to how they start up their development Pyramid application (they still continue to use pserve --reload development.ini). I think I'll combine your answer with the one below and add it to the postactivate file of virtualenvwrapper. Great respect for you; you've helped me countless of times in the past with Pyramid problems. Thank you. On Wednesday, 24 October 2012 13:44:57 UTC-5, Jonathan Vanasco 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 view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/qpVceXzBsiAJ. 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.
