I am the web developer for a new site that is coming up but there are also numerous other drupals sites I will be in charge of. The current setup for the other drupal sites is that they use Perforce (version system) to keep track of all changes done to the files of module and themes. Then they use a versioning module to keep track of all the content changes done on the site.
I was wondering if there is an all-in-one solution for drupal that can control all versioning in Drupal. I found the Version Control API but not really sure how to set all this up. I found the Live CSS module which lets a user edit the CSS but not sure how that using versioning as well.
If anyone can give me insight on how to setup my new drupal site or revise my current ones to have a all-in-one versioning control, what modules would I need, I would be most appreciative.
Thanks,
Chris
Comments
Multiple methods
Typically, folks don't use an all-in-one method to version Drupal assets; they use different methods for different asset classes.
With Drupal, we have four (4):
These should all be handled differently.
To backup you database, run the dumps through duplicity in the same way that you are with the file system. This way, you'll have older versions for both stored in the same place (preferably off-site).