[UPHPU] svn over wan

[Kenneth Burgener]

On 9/22/2009 2:09 AM, Chad Sollis wrote:
> however, when I try to connect using svn://localhost/repo or svn://192.168.0.150/repo 
>   or svn://my.hostname.com/repo it does not work, no real helpful  
> error messages either.
>
> am I missing something?  I have svnserver -d --local-port=3960 running  
> (I will be changing the port number from the default)
>   


Chad,

The svnserver default port is 3690, not 3960.  If you are not using the 
default port you will need to specify the port along with the host:
  svn://localhost:3960/repo
  svn://192.168.0.150:3960/repo
  svn://my.hostname.com:3960/repo

As mentioned previously, you will also want to check to make sure that 
any firewall running will allow you to connect to this port.


I would like to recommend using the Apache Subversion module 
(mod_dav_svn) over the svnserver.  There are numerous benefits of using 
Apache Subversion module verses the svnserver, such as being able to 
secure the traffic with HTTPS (snserver can be secured with SSH, but 
this is a pain to setup, maintain and use).  HTTP(S) is more 
firewall-admin friendly.  You can integrate the Subversion access into 
an already established web server, if needed.  Svnserver maintains it's 
password file in plain text, where Apache password file is htpasswd 
hashed.  You also get a built in web browser interface to your SVN tree 
with Apache.  And if you need it, apache does logging, svnserver does not.

On the flip side, if it is just you using it (and don't need the above 
benefits), svnserver is really easy to setup, and does have some small 
performance benefits.

You can read more about Subversion Server Configurations in Chapter 6 of 
the Subversion book 
[http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html].

For recommendations for using svnserver or apache read 
[http://svnbook.red-bean.com/nightly/en/svn.serverconfig.choosing.html]


Kenneth