On Friday, September 27, 2013 10:36:23 AM UTC-4, pavel.lyalyakin wrote: > > Hello Ben, > > > 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"? > > You can customize VisualSVN Server in > "%VISUALSVN_SERVER%conf\httpd-custom.conf" however, as far as I > understand your case, -- there is no real need for this. > > * I'm a bit confused by the case with port numbers you describe. Do > you mean that you used HTTPS on port 82? You can set VisualSVN Server > to work with HTTPS on port 82 or any other port you want which is > available. Or is this the case when you want to run the server both on > HTTP 82 and HTTPS 443? > > Yes, I want to run on both ports at the same time. I did this previously under our Apache2+SVN configuration on Linux without any problem.
> * We do not recommend to rewrite repository name since it can break > user authorization. You can rename the repository via VisualSVN Server > Manager console. I don't see any issues with that, in fact. Could you > please clarify what led the administrator to change the original > repository name? > Yeah, I figured as much. Basically, the repository was named after the company we work for. That name was later changed. When the admin setup VSVN, he named the repository using the new name. > > 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. > > As far as I understand your case, it would be the best solution. > Thanks. Ben -- 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 visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/groups/opt_out.
