Okay, I’m admittedly NOT a programmer or IT systems person. I’m a librarian by training, who has, through years of effort, become a web manager and information architect. So, when our programmers suggest some possible frameworks for our Drupal installation’s backend, I’m just clueless.
There is testing going on right now to create a backend CVS repository for maintaining our Drupal installation(s), I say “sure, why not!” Then, when terms like “clean build” start getting thrown around, I’m lost. Is using a CVS repository in this way simply a way to manage the Drupal files? I would have thought Drupal itself would have a way to manage versions and the versions of it’s modules, etc. Is this overkill to create such a backend way of managing one’s Drupal installation? Couldn’t we just make backups of all files and databases on a regular (hourly, daily) basis and restore the files if there is a problem. Doesn’t Drupal store, via Devel Module, who changes what and thus, in a sense, “versions” of what’s configured?
Also, our Drupal is installed in a manage cloud environment, Rackspace Cloud Sites. How does this proposed backend interact with the cloud?
So many questions… Can anyone who “speaks IT” help me understand these issues, please?
