[development] Site specific modules

[Lisa Sawin]

On Apr 29, 2010, at 8:42 AM, Nikola Kotur wrote:

> I completely agree with Justin, and can't recommend Git enough.
>
> Especially when a lot of different features are developed at the  
> same time. And it's very easy to check how different features work  
> together by creating new branch and than merging features in it.  
> It's so fast and easy, that I wonder how I ever coded without it...
>

I would love to hear some tips on managing changes to the database  
with git.  I'm comfortable with git and use it in my Ruby on Rails  
work, so I've been using it for my Drupal work, too.  When I'm working  
on a site, it's easy to dump my dev database and push it up to my  
production server, then simply replace the production database.  What  
do you do for a live site, though?  How can I merge new work on  
modules and their configurations in my dev database up to the  
production site?


Lisa

Lisa Sawin
lisa at lisasawin.com
www.wintersondesign.com
203.209.2408

-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.jpg
Type: image/jpeg
Size: 40337 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20100429/d7dbf17d/attachment-0001.jpg 
-------------- next part --------------