Closed vdubya closed 5 years ago
Step one is just getting dev separate from production. Discussed using migratable backups as a way to achieve this quickly and easily as a start, or @jmerlan may have some other magic up his sleeve.
@vdubya I've gone through the document that you posted and it really is just versioning for the Drupal code, so it doesn't version the database itself. I think we can continue with manual backups using cpanel as I have in the past. I don't think there really is a need to use git with Drupal unless we have custom modules we are developing. Thoughts?
@vdubya Can we close this one out? Unless we want to use git for versioning the Drupal code, I don't see it necessary at this point. It would make sense if we started developing custom Drupal modules to use Git for that code. It would be more beneficial to do full file/db backups periodically.Thoughts?
@vdubya Closing this one out. Please see comment above and reopen if needed.
https://www.drupal.org/node/803746
Also would be good to figure out how to create forks for replicating the site for different collaborative standards development purposes.