Posted by mpaler on May 3, 2010 at 7:02pm
In Josh K's documentation covering how to install an existing drupal site into pressflow/mercury he says:
"A quick way to get rolling is to install your site over the top of the existing Pressflow Drupal instance that comes with the Mercury EC2 image. This is good if you have a simple site, and aren't concerned with managing the codebase with SVN or other version control going forward."
This begs the question: How are people managing development flow and version control (dev > staging > production) using Pressflow/Mercury? Specifically, it would be great to hear how people are doing it on EC2.
Comments
...nevermind.
...nevermind.
I would also be interested to
I would also be interested to know how others are doing this. The mercury 1.2 installation I have already has 3 separate pressflow's (/dev, /test, /live) along with their own DB's. I've heard of people using symlinks to push from dev->test->live.
I'm also interested in this.
I'm also interested in this. We are just about to decide how we are going to manage changes from Dev -> Test -> Production.
Best practices for doing this in Drupal as well as best practices for Pantheon Mercury images would be great.
Thanks.
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com