3

Hi I am looking for a best practice staging workflow for a four level staging environement for drupal:

dev->test->pre-prod->prod

I found this quite informative thread already Applying Updates to Multiple Drupal Sites

As the Teams will change especially on the test upwards it has to be pretty straight forward.

  1. I guess we will move everting as far as posible through git or would rsync be better choice?

  2. Is there some way to maintain some kind of central stage configuration where you just maintain the server adresses e.g. in on central place

  3. How to move database changes without conflicting with productive content

Would be great if someone could share hints to some documentation of such a workflow.

Thanks in advance

Improve this question
5
  • Hi and welcome to Drupal Answers :) In it's current form this question is too broad to be answered, and is probably too localised to your specific situation to be useful for future visitors. Please consider breaking your questions down into ones that can be answered individually. Doing that will also make them more useful to future visitors without any extra effort
    – Clive ♦
    Sep 28, 2012 at 15:34
  • It's also one of the weakest features in Drupal right now...
    – mpdonadio ♦
    Sep 28, 2012 at 16:00
  • 1
    Hi Clive, I understand your concern but separating wouldn't really help. I did check out those two videos drupal.org/node/580026 and vimeo.com/33678298 which try to explain such a workflow, but they are not really easy to follow. Maybe someone already has written some kind of usable documentation about that.
    – macbert
    Sep 28, 2012 at 16:33
  • 1
    No problem, it was just a heads up really. I've seen quite a lot of questions like these get closed as not-constructive/not a real question because they cover a lot of ground and they're quite difficult to answer succinctly/objectively. It's definitely an interesting question though; I hope you get a good answer, but as @MPD mentioned this is an area where Drupal falls disastrously short at the moment. The Config Management Initiative for Drupal 8 will help going forward but it's a bit of minefield in current/earlier versions
    – Clive ♦
    Sep 28, 2012 at 17:27
  • 1
    BTW these might be of interest: drupal.stackexchange.com/questions/33403, drupal.stackexchange.com/questions/32659, drupal.stackexchange.com/questions/1335, drupal.stackexchange.com/questions/24777, drupal.stackexchange.com/questions/21243. The last one there will probably be very useful, it's got a lot of links to deployment recommendations for Drupal
    – Clive ♦
    Sep 28, 2012 at 17:33

2 Answers 2

Reset to default
1

Regarding #2, I would recommend using drush site aliases. See also the sync_enable example in Drush, which demonstrates how you can get Drush to automatically adjust your database settings when you move your db from prod towards dev. For moving configuration from dev to production, many folks use features; you might also want to look at ctools export bonus, which is built on much of the same technology.

Improve this answer
0

in the meantime we do have a quite robust workflow and toolset for deploying Drupal through a multistage environment.

We use: -Features, Strongarm and Drush on the Drupal side -Jenkins, Git, Rsync for the Deployment

If you are interessted in further details just send me a PM

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.