<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Handwriting";
panose-1:3 1 1 1 1 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="blue">
<div class="Section1">
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">No I do not. I use git for code and only code. Much of configuration (views content types,etc) for drupal is stored within the mysql
database. The database is not something that plays well with version control. (You don’t want git to have the “Data” e.g. specific Articles and such in the DB but you might want the configuration) .
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">The backup/migrate module facilitates complete copies of the database from production back to staging/devel. It does not require Git
access to do. <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">In Drupal 8 we’ll be excited to see much of this configuration information being able to be stored in the filesystem which is far more
version controllable. Then you’ll be able to choose configuration trees that could be managed with version control, but until then configuration is hopelessly mingled with content, and the line between them is both grey and subjective.
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">If you’re planning on using git to track configuration (not source code) then I’d encourage you to look at features as others have suggested.
It will take more to ramp up on than backup/migrate, but I was under the impression that you wanted to avoid having your site admins do that. Much depends on what kind of shop you are and what fits best with your current practices.
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">Dave<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">
<hr size="2" width="100%" align="center" tabindex="-1">
</span></font></div>
<p class="MsoNormal"><b><font size="2" face="Tahoma"><span style="font-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size="2" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma"> support-bounces@drupal.org [mailto:support-bounces@drupal.org]
<b><span style="font-weight:bold">On Behalf Of </span></b>Anthony<br>
<b><span style="font-weight:bold">Sent:</span></b> Friday, February 22, 2013 10:54 AM<br>
<b><span style="font-weight:bold">To:</span></b> <st1:PersonName w:st="on">support@drupal.org</st1:PersonName><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [support] Best practices for stage <--> productions</span></font><o:p></o:p></p>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">David when you say clones do you mean working with git?<br>
In our online study group at <a href="http://drupalistasgroup.com/">http://drupalistasgroup.com/</a> we have been exploring multi-sites and backup and migration strategies. As you said there are lots of strategies.<br>
Anyone is welcome to join us.<br>
<br>
Tony<br>
<br>
<o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">On Fri, Feb 22, 2013 at 8:35 AM, Metzler, David <<a href="mailto:metzlerd@evergreen.edu" target="_blank">metzlerd@evergreen.edu</a>> wrote:<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">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<o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><br>
-----Original Message-----<br>
From: <a href="mailto:support-bounces@drupal.org">support-bounces@drupal.org</a> [mailto:<a href="mailto:support-bounces@drupal.org">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">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> ]<o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><br>
<br clear="all">
<br>
-- <o:p></o:p></span></font></p>
<p><b><i><font size="2" face="Lucida Handwriting"><span style="font-size:10.0pt;
font-family:"Lucida Handwriting";background:white;font-weight:bold;font-style:
italic">Anthony Stefan Maciejowski</span></font></i></b><o:p></o:p></p>
<p><b><i><font size="2" face="Lucida Handwriting"><span style="font-size:10.0pt;
font-family:"Lucida Handwriting";background:white;font-weight:bold;font-style:
italic"><a href="http://www.Tony-Mac.com" target="_blank">www.Tony-Mac.com</a></span></font></i></b><o:p></o:p></p>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
</div>
</body>
</html>