I run my own server at home.. complete with 42U rack I use it for development of projects and common network activities.

Soon I will be moving things around, and I , like many, get in the habit of wanting to change things up and play around. I've loosely used svn for things, but want to make it a vital part of my SDLC and workflow.

Here is my idea, keep in mind I work as a single developer.

Setup::
Start the repo with current version of website.
Have 3 folders: dev/staging/live
Checkout the current repo to dev/staging/live folders

When I want to make changes
1) Update dev folder to current version,Make changes to the dev folder when I am done and want to show the client
2) Commit changes and update staging server so the client can view
3) whenever changes are accepted update the live server

Sounds about right to me.

So what are your workflows using version control? Suggestions and critique are welcomed.

Wow, you have put a LOT more planning into this than I did. My idea of workflow & version control involves a lot of cp -R, & 2 separate 1u servers, or centralized/shared storage. As well as directories named New, Old, & current. Current as of when? I don't know, check the file details. lol

^ that was my approach as well.

Now everything is setup.

I use Webdrive to map remote project folders onto my pc, then the process begins.

1. I use the awesomeness that is ZSE to edit files in the trunk and view the changes on the dev server (only available to internal network).

2. When I want to show the client, I commit the changes to the trunk, then run a shell script i made called svn_sync.sh which merges the trunk into the staging branch then commits the staging branch.

The client can now look at the changes on the staging server, which is available by password.

While I still work on my dev server without any disruptions on the staging or live server.

3. When he approves changes, I run svn_sync.sh again , this time for the live server, which merges the staging branch into the live server and commits it.

Now the changes are live.

It is nifty, since there is no single point of failure, I have a local cache of the trunk, the repository is on my windows 2k3 server, and the servers are located on the linux server. I can always revert to a diff revision, and I never have to edit the production server directly.

I'm pretty happy with everything.