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
Drupal Architects, Drupal Programmers, Any one who is looking at solutions to maintain their Production server updates.
Comments
Good topic. All the best.
Good topic. All the best.