On Fri, May 22, 2015 at 8:14 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> >
>> Thanks - does this include a working mod_dav_svn for http access using
>> apache?
>>
>
> Les,
>
> I thought you used to use SVN Edge (which I maintain), so that is why I did
> not recommend it. I assumed you were not considering it for a reason.
I think we may have once had support with Collabnet but just used the
stock Centos binaries, and later switched to Wandisco to use their
authentication proxy against AD because it was getting cumbersome to
manage passwords and the authz file. I wasn't very involved in
choosing that part but don't think there were any problems involved
before or after the change. But, we still have a mix of http:// and
svn:// access for an assortment of complicated reasons and I'm just
looking to move it from CentOS5 to something newer without breaking
anything.
> SVN Edge includes everything, but that might not be what you want. It does
> not use or replace the packages that come with CentOS. Instead it provides
> a full private stack of everything. It also needs Java installed to run the
> web GUI.
That may be a wise choice if the issue is really a bug in the stock
version's mod_dav module. Given the redhat/centos policy of not
changing behavior of things for the life of a major revision it's hard
to guess when/if it might be fixed. But, the path of least resistance
here might be to move to CentOS6 where the wandisco 1.8.x rpms would
just drop in and work and we'd be good for several more years with
minimal changes to the configuration.
Thanks for commenting, though - I'm still trying to understand all of
the options.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2015-05-22 17:19:51 CEST