By drozzy on

Dear Drupalers,
I was wandering if you could advise me.
You see, I got a project to develop a site for a small business.
What I am thinking of doing is what I did before. However this is what usually happends:
-Upload drupal to site. Install modules and things.
-Backup.
-Tinker with the things/code.
-Backup.
-Tinker with things/code.
-FORGET to backup.
-Tinker some more -> Crash. Loose a week of work.

I was wandering if there is any way of somehow setting up some kind of CVS system for my site. So that I can roll back some minor changes I made. Even better if I could roll back anything.

Or perphaps you could suggest a better workflow.

I think that my tinkering with a live site until it crashed is not a very good idea. Yet I keep doing it since performing a FULL backup before I make any minor change is really pain-in-the-a**.

Any advice is welcome
Thank you!

⋅ Categories: Drupal 5.x

Comments

davemybes’s picture

davemybes commented

The way I usually do things is to run a local server and keep a copy of the live site on that server. Then I test all modifications locally before uploading/changing anything on the live server. To run a local server you can download one of the many server packages that include Apache/PHP/MySQL. Personally, I use the Uniform Server.

______________________________________________________________________________________________________
Need help? Check the FAQ and the Handbooks first.

______________________________________________________________________________________________________

drozzy’s picture

drozzy commented

thanks. I was thinking of doing that.
But I imagine down the road I will not always keep this local copy. As for example I will have other clients to work with.

drupalnesia’s picture

drupalnesia commented

This is not as simple as you think. Why? Because when you change something in Drupal you may change the code (PHP, .htaccess) and/or DB too! So, u don't need to do FULL backup (this will including your email too).
What u need only backup the public_html/ and your DB. Also you must have 2 environment system/computer: production and development except you believe you will not brake something in the production server :)