Version Control with Subversion - Login

Server ConfigurationWhy you might want to avoid it:• By default, only one authentication method is available, the network protocol is notencrypted, and the server stores clear text passwords. (All these things can bechanged by configuring SASL, but it's a bit more work to do.)• No logging of any kind, not even errors.• No built-in web browsing. (You'd have to install a separate web server and repositorybrowsing software to add this.)svnserve over SSHWhy you might want to use it:• The network protocol is stateful and noticeably faster than WebDAV.• You can take advantage of existing SSH accounts and user infrastructure.• All network traffic is encrypted.Why you might want to avoid it:• Only one choice of authentication method is available.• There is no logging of any kind, not even errors.• It requires users to be in the same system group, or use a shared SSH key.• If used improperly, it can lead to file permission problems.The Apache HTTP ServerWhy you might want to use it:• It allows Subversion to use any of the numerous authentication systems already integratedwith Apache.• There is no need to create system accounts on the server.• Full Apache logging is available.• Network traffic can be encrypted via SSL.• HTTP(S) can usually go through corporate firewalls.• Built-in repository browsing is available via web browser.• The repository can be mounted as a network drive for transparent version control(see the section called “Autoversioning”).Why you might want to avoid it:• Noticeably slower than svnserve, because HTTP is a stateless protocol and requiresmore network turnarounds.• Initial setup can be complex.158