We recently had a project that needed to have subversion installed on Media Temple's DV Rage server. Our first attempt was using the svn+ssh protocol which turned out to be a bit more involved than we expected. Ultimately the solution requires the creation of a public key and sending that key along with your credentials each time you connect to the repository. After digging a bit more, we realized we could just use http using the mod_dav_svn apache package. Even better is that the developer tools now come with this package out of the box. Read more about the packages here: http://kb.mediatemple.net/questions/807/%28dv%29+3.5+Tech+Specs+-+Developer%27s+Tools+package+listing Some great information on how to setup SVN through http by modifying your vhosts file can be found here as well. http://blog.hellm.com/post/9
EDIT: We ran into an issue once we tried to connect to the repository with svnX GUI and a quick google search led to this solution:
http://www.pyrusmalus.com/blog/archives/2006/11/06/subverting_certificat...
Excerpt -
open terminal and enter the normal svn command first:
svn list https://svn.sourceforge.net/svnroot/redshed
Up comes the warning:
Error validating server certificate for 'https://svn.sourceforge.net:443':
- The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually!
Certificate information:
- Hostname: *.sourceforge.net
- Valid: from Dec 8 13:40:07 2005 GMT until Feb 7 13:40:07 2007 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: 49:b8:cb:87:04:8c:49:39:45:83:dd:4c:cf:c7:54:57:b0:9e:84:5d
(R)eject, accept (t)emporarily or accept (p)ermanently? p
Now you can press ‘p’ to accept the certificate, at which point the list command shows the familiar listing:
branches/
tags/
trunk/
Now that the certificate has been accepted, you can go back to svnX and connect to the repository in all its GUI goodness.