Can you post the changes you made to httpd-custom.conf? I'm trying to do the same thing with limited success. Thanks. . .
On Sep 17, 8:23 pm, ". ." <top...@operamail.com> wrote: > Thanks for the ideas, Carey. With some work, I managed to get VisualSVN's > Apache instance to proxy to the wiki, as this way we only have one Apache > instance to manage instead of two. I also figure it's more efficient for the > sake of VisualSVN, since that'll be the more demanding service of the two. > > But I did manage to do all the customization within httpd-custom.conf by > setting up VirtualHosts, so I didn't have to modify httpd.conf. Seems to > work. > > Trevor > > > > Carey Bishop wrote: > > > It's probably easiest to make the wiki instance of Apache run on port 443, > > and proxy any requests to a certain URL (such as /svn/) to VisualSVN Server, > > rather than the other way around. The only reason for saying this is that it > > can be difficult to get Windows binaries of the modules that are the correct > > version for binary compatibility with the VisualSVN instance of Apache, > > where as the wiki installation probably has those modules there already. > > > I have in the past been successful at using mod_proxy to do from the > > VisualSVN Server instance, by installing the binaries for mod_proxy and its > > dependencies, and modifying httpd-custom.conf to include them. You'll then > > need to monitor the Application log as VisualSVN Server starts up to make > > sure that the modules were loaded successfully. > > > Any standard guides for installing mod_proxy on Apache should give you all > > the configuration details you need. > > -- > _______________________________________________ > Surf the Web in a faster, safer and easier way: > Download Opera 9 athttp://www.opera.com > > Powered by Outblaze
