[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Configuration files...

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-01-08 22:03:47 CET

On 1/8/07, Brian Erickson <erickson@bauercontrols.com> wrote:
> Hi all,
> I'm trying to understand how Subversion deals with system-wide configuration
> properties and can't figure it out. I've read the docs but am still
> clueless. I'm hoping someone can help me.
> I'm using windows XP and all my users will access the repository using the
> FILE:// syntax.
> 1) Is there a way to set options that every user accessing the repository
> will have?
> Specifically, I'm looking to ignore things like object files and such as
> well as an editor for when the -m option is missing.

Client configuration is per-user. There is currently no way to set a
particular configuration from the "server" (I put this in quotes as
you have no real server when using file://).

> 2) If it's possible, where do these file(s) go? what is the format?

Each user's config is in %APPDATA%\subversion\config . It's a
plain-text file. Documentation is included within.

> 3) Right now, I've locked down branches in the tags folder using the
> pre-commit hook. Can I do the same thing in the "authz" file (remember I'm
> using the FILE:// syntax)?

Using file://, it's all or nothing - users either have access to the
repository (via the host OS's permissions - NTFS & share permissions
in your case, I'm guessing), or they don't. This means they can very
easily hose the whole setup.

file:// really isn't suited to a multi-user environment - it's best
for single-user setups, and testing/debugging. You really ought to
consider serving via svnserve or Apache.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 8 22:04:06 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.