Converting from simple installation to CVS on shared server - various best practices?

jsibley - May 25, 2009 - 03:52

I have a working site v6 site on a shared server. Currently, I only have a live site and am the sole developer. I add modules that appear appropriate, modify content, and perform upgrades.

I would like to do the following:

- recreate my site using CVS, so that updates are easier
- use drush to further automate updates
- have some sort of test version on my shared server, so that if adding a module or updating breaks anything, my production site is still intact. I'm thinking, based on what I've read, that I should create a test subdomain
- I'm not sure if SVN is overkill, but I'm willing to use it if it makes sense

I'm not sure of the best way to move from my current setup to the CVS based setup that includes a test version of my site.

My website is not updated frequently by others (there may be occasional comments to a blog post at some point), so I can easily put the site offline, make modifications on a test version of the site, and copy the test site to the production site once I know everything is working. I have access to ssh but am not very familiar with linux.

Is there an obvious sequence of steps I should follow? I've seen posts that suggest some of the pieces, but nothing that covers all of this. I'm willing to use the deploy or cvsdeploy modules if that will help.

I'd appreciate any help.

Possible approach

jsibley - May 26, 2009 - 11:34

Here is the approach I'm thinking of taking.

1. Create subdomain for test site
2. Create new Drupal site from scratch in test site using CVS
3. Make sure test site isn't indexed by search engines (password protect?)
4. Copy whatever necessary from production site to new test site trying not to break anything (hopefully I can follow directions I've found on updating a site to CVS for this)
5. Make sure test site works
6. Copy test site to production site (possibly using rsync approach I've seen documented?)

Hopefully, this will all work. If it does, I'll add links to articles I've used. I'm open to any recommendations in the meantime.

I'm not sure where SVN should fit in this process. Hopefully I can retrofit it if I haven't figured that out before I start.

 
 

Drupal is a registered trademark of Dries Buytaert.