Even with something basic, version control is too useful to just omit. I decided to go with the latest version of Subversion (http://subversion.apache.org/) because
- I've administered small scale repositories before, and learning version control admin isn't an objective or something I want to spend any time on.
- With TortoiseSVN (http://tortoisesvn.tigris.org/) it integrates nicely into Windows Explorer, and it's easy to use
- I haven't tried the Subversion Eclipse plug in, but once it's up and running, I'll add this to the IDE.
I've installed Subversion on the Server machine, and was pretty impressed with the ease of use of Subversion 1.6.13. Previously at work I used a file repository and IIRC it was version 1.4, but setting this new release up as a web server repository proved stunningly easy, simply following the wizards. The browser based front end is pretty good. So now I've got a basic installation up and running, only two users (Admin and Dev users), and my first few files booked in, but with the ability to create multiple repositories as I need them.
Repository per project ?
I did have an internal debate, whether to go for 1 repository for all projects, or 1 repository per project. I checked the first few links from a Google Search, and, at this point, the 1 repository per project model seems easier. I don't have any requirements for hook scripts or other cross project concerns at this point, so the admin overhead isn't a consideration (yet)
So from now on, even dev files, Eclipse settings etc can be tracked and rolled back - useful when I'll be doing so much experimenting over the next few weeks. Nice.
No comments:
Post a Comment