AFP548 Changing the world one server at a time.

Subversion Repository Setup

Home › Forums › OS X Server and Client Discussion › File Serving › Subversion Repository Setup

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #370369
    Siegfried
    Participant

    Hello All,

    In a recent deployment of Mac OS X Server 10.5 (Leopard), we have come
    across an issue with the way DAV is handled by the Server Admin
    application.

    We enabled the 4 required modules for Subversion, dav_module,
    dav_fs_module, dav_svn_module, and authz_svn_module. Then we created
    a new SSL site on port 443 and in the
    /etc/apache2/sites/0001_any_443_site.com.conf file we appended our
    custom information:

    <Location /svn>
           DAV svn
           SVNParentPath /Library/WebServer/Subversion/repos
    
           # Our access control policy
           AuthzSVNAccessFile /Library/WebServer/Subversion/conf/svn-authz-access
    
           # How to authenticate a user
           AuthType Basic
           AuthName "Subversion Repository"
           AuthUserFile /Library/WebServer/Subversion/conf/svn-auth-file
           SSLRequireSSL
    
           # Only authenticated users may access the repository
           Require valid-user
    </Location>

    This is worked until a setting in the GUI (Server Admin) was changed
    and it updated the configuration file. It reformatted it and removed
    SSLRequireSSL, which is fine, but it also set DAV to off. Of course
    with “DAV off” instead of “DAV svn”, Subversion would not work, so we
    had to manually edit the configuration file and have Apache reload it.

    Is this possibly a known issue/feature with Server Admin? Are we not
    supposed to use the GUI once we changed the configuration file?

    Is there some way we can just tell the GUI not to modify the “DAV”
    line? I mean, it almost works, except for the fact that that line
    gets changed.

    Thanks.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.