|
I want to create a subversion repository for my development team. The question is : Where ? Two options : 1.Local (at home) on a server like NAS... benefits : coast weakness : security ? 2.On dedicated server on professional cloud benefits : security / avaibility weakness : coast Have you other option ? What's the best option you think ? Can you tell me your choice and the + and - for each option ? Thanks :) |
|||||||||||
|
Questions on Answers OnStartups are expected to relate to startups within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
|
You should look into a decentralized scm actually like Mercurial (easy to use) or Git (more powerful, but also a bit more complicated to use). Benefits: - all devs have the complete history - no central server which does fail - no 3rd parties access your code, except you look for Bitbucket - free of charge, no hosting necessary - easy set up if you would like to have a canonical repo in your office (network path is enough) - always available, even without internet connection Drawbacks: - your team needs to learn it This link does show how to work with git in a proper way: http://nvie.com/posts/a-successful-git-branching-model/ I was switching for these reasons to Mercurial and Git and I am not looking back. SVN is still great because it is really easy once set up. But on the other hand, I don't want to pay or maintain for another server. If you force me to chose one of your options, I would go for a hosted one. They care for backups and such. But only, if they allow me to export the whole repos from time to time - don't trust anybody when it comes to your code. Their backup may fail too. |
|||
|
|
