Setting up a code repository

[matrisking]

I'm looking to set up a code repository that I can access from multiple machines within my home network, but not online. Right now I'm considering two options:

1) Setting up NAT on an external hard drive attached to this guy
2) Setting up a cheap, small form factor PC.

Pros? Cons? Will it make much of a difference either way? Vague, I know, but this is my first time setting up a code repository, and I'm not sure what I should be taking into consideration here. Performance won't be an issue, so I don't think SSD would be necessary, but if a small form factor PC will support RAID, then mirroring a pair of drives would be preferable. Just looking for any general feedback people might have regarding this decision.

Thanks!

 

[Shockey]

www.dropbox.com

 

[danswartz]

Get a low power atom with two drives in raid1.

 

[dashpuppy]

Get a low power atom with two drives in raid1.

Best solution, those Buff units = garbage proprietary usb

 

[ripken204]

define repository... git? or just local storage or dev server?
if any of the above, build a cheap dev box. if it's just code then the files are going to be small and will transfer fast even on an atom

 

[brutalizer]

Dropbox is Free and good for your purpose

 

[matrisking]

define repository... git? or just local storage or dev server?
if any of the above, build a cheap dev box. if it's just code then the files are going to be small and will transfer fast even on an atom

Not necessarily git, probably SVN.

Did a little googling, it looks like people have used SVN with Dropbox, so that might work. It doesn't work well once you start having multiple users modifying code, but since I'm just using it to keep a couple of my own machines in sync that would be fine. If for some reason that doesn't work for me, I'll look into building an atom-based machine.

Thanks!