![]() It's simplest to group these by functionality (for example, you could create one features module which contains all the configuration necessary for the blog section of your site).Īfter making changes, run drush features-update-all to export the configuration from the database to code. After setting up your site's views, content types, variables, and other configuration, you would use the Features module to export these to code as a series of special modules in sites/all/modules/features/ and from there commit them to git. In Drupal 7, the best practice is to export all possible configurations using the Features module, so that it can be tracked and versioned in git. ![]() You'll need to adopt specific git practices to make this work smoothly.ĭrupal with Git: Best Practices Drupal 7 + Git best practices Once all your updates are in code, you're ready to use git to prepare for and manage your testing and deployment process. Any further steps necessary to test or deploy the new version should be clearly described in the ticket description. The changesets should be self-contained, and perform all necessary database changes in code via update hooks, features (Drupal 7), or the configuration management system (Drupal 8/9). To make this work, it's best to use an issue tracker with a ticket for each user story, and to make all changes to your site on a separate git branch labelled with that ticket number. Find the commit where a given change was made.Remove a feature that didn't pass review.Before a deployment, you occasionally need to revert from a release branch a ticket that didn't pass review.You occasionally need to do hotfixes for urgent problems directly on the production site.You review releases (continuous integration, user acceptance testing, change approval board, etc.) before deployment.You want to do regular releases of whatever tickets are ready. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |