We have had a server running Apache2+SVN on a Linux System for over 4 years. The initial install for SVN was on Port 82 and that go linked in for quite a few svn:externals. During a server rebuild it was put on a 443 (standard https), and a redirect for Port 82 was added to keep it working. In both cases the SVN URL was otherwise unchanged. This was all initially with SVN before the ^/ scheme for svn:externals was around - so the svn;externals refer to a FQDN URL - e.g. https://my.server.com/svn/myrepo:82 and https://my.server.com/svn/myrepo (after the change). More recent revisions have the ^/ usage, and modifying the repository between dump/load is not an option (too many working copies around; and it's taking long enough to reload the repository as it is).
Recently, it was decided to move it to a Windows Server using VSVN. The administrator set it up to use Port 8443; but he also changed the basic repository name. I know VSVN is basically a nice wrapper and manager around an Apache2+SVN install on Windows; does it still use the Apache2 configuration files? And is it possible to put in the port 82 support I did before and potentially do a mod_rewrite to change the repo name from "myrepo" to "newrepo"? TIA, Ben P.S. I am trying to convince him to change the repo name back, and put it on port 443 instead of 8443 to help simplify a lot of this. -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/groups/opt_out.
