<div dir="ltr"><p dir="ltr">To be blunt this is an area that Drupal has some issues with because of how how content and configuration are stored. Great strides are being made in the Drupal 8 release and there are ways to build solutions now that will meet your needs. </p>
<p dir="ltr">There are methods for moving content from a staging environment to production There is a lot of working happening around the UUID Module <a href="http://drupal.org/project/uuid">http://drupal.org/project/uuid</a>. </p>
<p style>The Features module is a great ways to export configuration along with the Strongarm Module (<a href="http://drupal.org/project/strongarm">http://drupal.org/project/strongarm</a>) . Using GIT helps to manage code but there are systems out there. </p>
<p style>Welcome to Drupal and I hope this helps. </p><p style>-Steve </p>
<div class="gmail_quote">On Feb 22, 2013 9:35 AM, "Metzler, David" <<a href="mailto:metzlerd@evergreen.edu" target="_blank">metzlerd@evergreen.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
You should really check out<br>
<br>
<a href="http://drupal.org/project/backup_migrate" target="_blank">http://drupal.org/project/backup_migrate</a><br>
<br>
There are lots of strategies out there, but I tend to follow the following strategy.<br>
<br>
* Set up identical but separate staging/development environments.<br>
* Do periodic clones from production back to test/staging.<br>
* use the export import features that are provided with many key project (e.g. views, cck, panels) to move larger config changes to prod, and do the rest (tweaks) manually, first in test, then in prod.<br>
<br>
Many people would talk about using modules like features, etc to facilitate deployment, but I've found that most push config synchronization strategies create more work than they save.<br>
<br>
My 2 cents anyway.<br>
<br>
Also if you're a UNIX admin and new to the community.... you really need to get and install drush. <a href="http://drupal.org/project/drush" target="_blank">http://drupal.org/project/drush</a><br>
<br>
Dave<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:support-bounces@drupal.org" target="_blank">support-bounces@drupal.org</a> [mailto:<a href="mailto:support-bounces@drupal.org" target="_blank">support-bounces@drupal.org</a>] On Behalf Of Zyumbilev, Peter<br>
Sent: Thursday, February 21, 2013 9:54 PM<br>
To: <a href="mailto:support@drupal.org" target="_blank">support@drupal.org</a><br>
Subject: [support] Best practices for stage <--> productions<br>
<br>
Hi,<br>
<br>
I have more than 10 years of web admin/dev experience but I am just<br>
starting with drupal. I am about to set stage/dev environment for the<br>
first project. Both production and stage are Unix(Freebsd), I have full<br>
root access. What should be the best practices I should follow.<br>
<br>
So far I found these:<br>
<br>
(1) <a href="http://drupal.org/project/drush_ctex_bonus" target="_blank">http://drupal.org/project/drush_ctex_bonus</a><br>
(2) <a href="http://community.aegirproject.org/" target="_blank">http://community.aegirproject.org/</a><br>
<br>
<br>
What do you advise for best practices ? Nice to have, but not a must is<br>
to be simple for the web developers e.g "press button sync": i.e they do<br>
not need to contact for export, they do not need to go under ssh and use<br>
git/svn.<br>
<br>
<br>
Thanks,<br>
<br>
<br>
Peter<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</blockquote></div>
</div>