On Mon, Mar 19, 2012 at 5:06 PM, Michael Hüttermann <mich...@huettermann.net > wrote:
> Hello, > > I'm wondering if there is any strategy for temporary preventing people > from committing to a svn repository, without the person who sets the hook > (or sth similar) being the admin of the svn repository. Thus, in this > case, there is no option to directly access the /hooks/ folder. > > A "poor man's" option could be working with locks. But, recursively > locking a large repo path could be inefficient, and locks can be stolen > anyway. So it looks like the wrong approach from many perspectives. > > Any idea for preventing commits, for a specific time, without being able > to directly accessing the hooks folder? > > If the access is through svn+ssh and you can be granted access to the authorized_keys, you can tweak it to read-only. If it's an Apache based access with HTTPS, you can manipulate the Apache config (which requires reloading the Apache server configuration, or control of a .htaccess file) Means vary depending on which technology you use and what you *do* have access to.