So, even in distributed international team, we used SVN authentication, via HTTPS, for safety.Īll other Enterprise features are absolutely not needed, simply because people playing the role of administrators can access the server's host locally.
If you use passwords, the are not stored anywhere, like with in a decent system (hash functions are stored, finding out passwords is cryptographically infeasible). Why not? Nobody from outside worlds cannot access it anyway, and all the moves are recorded. We usually worked on a local domain without passwords, to make it less annoying. Here is the idea: I advice to use only the server authentication, not Windows.
#ANKHSVN OR VISUALSVN LICENSE#
Developers can decide by themselves.Īs far as pricing and license are concerned:
Seriously, you should only recommend developers something, but never enforce any particular client. First, it's too intrusive for me, and, more importantly, what to do with non-VS development? To me, the ideal solution is TortoiseSVN. I, for example, hate the idea of Visual Studio plug-in. If the team is distributed, I would recommend dedicated development Linux server and HTTPS (you will also need a certificate, at least self-signed).Īs the the client SVN, I think this is a matter of decision of every individual developers. It also depends on this: is your team distributed, or it is in one LAN. If you are asking about SVN server, I tried many and found that the two very best are:ġ) SVN Server for Linux 2) for Windows, Visual SVN server is by far the best.