2

I am wanting to work on a project from multiple computers on the same network. If it matters, I am using Code::Blocks across multiple OSes.

What would be a good way to do this? Set up an SVN server on one of the computers?

4 Answers4

4

Please, stay away from Subversion.

The best solution is using a DVCS (Distributed Version Control System). There are many of them available, while the most famous are Git and Mercurial. After you understand the basic concepts, they are far easier, faster and more powerful than SVN. They are also trivial to setup (while SVN requires a central server, which requires more work and some infrastructure).

Personally, I prefer Hg over Git. On the other hand, I realize that GitHub website and its community is larger and better than BitBucket.

I highly recommend reading Hg Init: a Mercurial tutorial, written by Joel Spolsky. If you feel like reading, I've also written Things you should know about Mercurial in my blog.

Related questions:

Community
  • 1
  • 1
Denilson Sá Maia
  • 47,466
  • 33
  • 109
  • 111
  • Note, however, that you don't need BitBucket in order to share your commits in your local network. Heck, you don't even need a central server (although that is damn handy)! You can simply run `hg serve` each time you want to "serve" your commits to another machine. Well, you don't even need network connectivity (see `hg bundle`). However, I agree that a central server makes things a lot simpler and streamlined. – Denilson Sá Maia Jul 22 '11 at 18:15
1

The simplest route would be to use Git across the multiple machines, since that way it won't be OS-dependent and you won't need a centralized repos (as you would if you went with SVN). Because setting up Git is beyond the scope of this answer, I would point you to this answer to cover the setup that'd work for you: Git for beginners: The definitive practical guide

Community
  • 1
  • 1
Eric Caron
  • 6,181
  • 1
  • 24
  • 26
1

It will depend on your preferred flavour of source control system but since you've mentioned SVN, I'd just go and grab Visual SVN Server. It's super easy to get up and running (allow 5 minutes), free and will work just fine across your network. I run it in both a large enterprise environment on a server with hundreds of repositories and users and on my local machine and it works equally well in both scenario.

Troy Hunt
  • 20,345
  • 13
  • 96
  • 151
0

I use SVN, and I'm happy with it, though it does require a central server, I just use my 'always on' web server.

That said, I believe the trend is towards GIT, so I'd probably use that if I was starting afresh.

Snips
  • 6,575
  • 7
  • 40
  • 64