Best Practice Workflow for Git and Drupal ?

Ok, I'm putting together a plan to implement Git for the first time in our environment for Drupal development.

We will have a Dev, Staging and Prod. on separate physical boxes.

Can't use a public/commercial Git server, so we will have to stand up a Git server ourselves.

Attached is the initial draft of the network/workflow:

1) All coding done on dev (drupal.ourwebsite.com)
2) Pushed to Staging
3) Finally, pushed to Production


1) Am I on the right track?

2) Do content authors edit and create content directly in Production? Or does their edit have to go through Git version control?

3) Installing/activating modules part of the version control ? Or would we be installing/activating across all three boxes when a module is approved?
ii.JPG
sandshakimiAsked:
Who is Participating?
 
Aaron FeledyConnect With a Mentor Drupal Developer and ConsultantCommented:
Correct.
0
 
Aaron FeledyDrupal Developer and ConsultantCommented:
Database changes won't be included in the git workflow. Much of what Drupal does is in the database, so those changes will need to be manually applied on each system. This includes adding/editing content, enabling modules, changing settings, modifying menus, and just about anything that is done through the Drupal admin interface. Basically, yes, content should be managed on the production server. The only thing that will go through your git workflow will be actual code changes.
0
 
sandshakimiAuthor Commented:
So in essence, the value of Git version control is for HTML, CSS, JavaScript and PHP edits that don't involve database/administrative transactions ?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.