Maintaining the codebase and updates of a Drupal Website

Implementation and Config

Drupal stores most of the configurations and settings in the database. Deploying and Managing a Drupal website requires both code updates as well as interface updates. Changing permissions, adding fields to your content types, modify an existing view, installing and configuring a new module are some of the typical interface updates that needs to be moved from the Development Server to the Test servers and then further in the Live servers. In this session I would like to present solutions that would facilitate the update process to be people independent and totally maintained under version control. The topic covered would include:

  • Modules and approaches to ease out the Maintenance of any Drupal website
  • Usecases of Drush, Features, Strongram modules
  • Scripts that get triggered in update.php
  • A brief note on the functionalities and status of these modules for Drupal 7
  • Use of SVN or CVS versioning system to maintain the codebase
Intended audience: 

Drupal Architects, Drupal Programmers, Any one who is looking at solutions to maintain their Production server updates.

Questions answered by this session
Question 1: 
How to have a Drupal update process that is people independent and totally maintained under version control?
Question 2: 
How to use Drush to improve the Update Deployment Process for a Drupal website?
Question 3: 
What are Features and Strongram modules?
Question 4: 
How to use update.php to trigger database script updates? What are the cache flush routines that need to be called after the database updates?
Question 5: 
What are status of Drush, Features modules in Drupal 7?
Your rating: None Average: 3.3 (18 votes)


Good topic. All the best.

Good topic. All the best.

Diamond Sponsors

Platinum sponsors


Gold Sponsors

Drupal Connect
Treehouse Agency
Chapter Three