[development] Deployment process

Ken Winters kwinters at coalmarch.com
Fri Jan 29 16:53:28 UTC 2010

Where possible, do everything in code rather than the database.   
Trying to merge two databases is a giant
pain, but pushing new code and running update.php is fairly painless.

If you do have to make database changes after the client has already  
entered data, you'll want to script it (often
using an importer).

- Ken Winters

On Jan 29, 2010, at 11:47 AM, Stewart Birch wrote:

> Hello all
> very early on in my Drupal learning process but have been asked to  
> come up with a solution where the client will be entering content on  
> the production site and we may very well be making structural  
> changes ( css etc )
> on DEV and changes to the site setup  ( for example a page name or  
> somesuch ) , is there a way to seperate the data entered for content  
> types from everything else so when deploying a site to production we  
> can do so without worrying about content being lost.
> Thanks
> Stewart
> http://www.flickr.com/people/mrbirch

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100129/5408aa85/attachment.html 

More information about the development mailing list