my preferred solution right now is: merge sourcecode into a 'current_deployed' tag/branch use fabric/fabfile to ssh into the server , checkout the build, install it into the virtualenv using 'development mode', set a few symlinks, and relaunch the app
i decided against running everything through an app that is installed into the virtualenv site-packages directory. my production deployments mix pyramid + twisted + http + some java , so I prefer having everything consolidated into the single directory structure that correlates to the source. it's totally a preference, but I like the 'self-contained' world that replicates itself. -- 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.
