In a nutshell: http://www.svn-access-manager.org/
Basically, store all your settings in a database and generate the config files; just use a simple web front-end to edit the database and control/log changes that way. The svn access manager provides a good starting point, modify and tweak as needed.
-----Original Message-----
From: Cooke, Mark [mailto:mark.cooke_at_siemens.com]
Sent: Monday, May 09, 2011 11:19 AM
To: users_at_subversion.apache.org
Subject: How to control changes to path-based auth file?
Dear list,
I was wondering how other (probably corporate?) svn users control and log changes to your path-based auth file (and other svn web settings)?
I was thinking that I could use svn and the auto-website-update FAQ
(http://subversion.apache.org/faq.html#website-auto-update) to control access by allowing named users access to the relevant repo... However this seems a little clunky and 'overkill' for what we have.
We also use `Trac` and there are a couple of trac-hacks:
* http://trac-hacks.org/wiki/SvnAuthzAdminPlugin
* http://trac-hacks.org/wiki/TracSvnAuthzPlugin
...that enable editing of the path-based-auth file through Trac but neither include any versioning (for auditing purposes).
Can anyone recommend any other routes?
For information, we use Trac and subversion, served from windows server via apache...
Many thanks,
~ mark c
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect_at_principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.
While this communication may be used to promote or market a transaction
or an idea that is discussed in the publication, it is intended to provide
general information about the subject matter covered and is provided with
the understanding that The Principal is not rendering legal, accounting,
or tax advice. It is not a marketed opinion and may not be used to avoid
penalties under the Internal Revenue Code. You should consult with
appropriate counsel or other advisors on all matters pertaining to legal,
tax, or accounting obligations and requirements.
Received on 2011-05-09 18:30:53 CEST