Forum Moderators: phranque
/srv/svn/support
/srv/trac/support
I currently have one password file in /srv/.htpasswd, which means all developers can access all projects. It's not a huge deal as it's for internal use at work, mostly for prototyping.
At some point I'd like to re-configure it so that I can control access on a per project basis. I've written some custom Python scripts that automate most of the work in creating Trac projects and Subversion repositories, to save me lots of typing!
So /etc/httpd/conf.d/subversion.conf is:
<Location /repos>
DAV svn
SVNParentPath /srv/svn # Limit write permission to list of valid users.
<LimitExcept GET PROPFIND OPTIONS REPORT>
# Require SSL connection for password protection.
# SSLRequireSSL
AuthType Basic
AuthName "excds"
AuthUserFile /srv/.htpasswd
Require valid-user
</LimitExcept>
</Location>
My problem is that each time I create a new Trac project/SVN repo pair, I don't want to modify existing Apache's config or create a new .conf file. I absolutely want to avoid having to restart Apache to re-read configuration.
I know I could use authz,but again that relies on specifying a different password file for each Location in a .conf file.
Is there anyway to get what I want without modifying Apache configuration and without restarting Apache?
Thanks