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

Re: WinXP Env - successfully using repos WITHOUT SVNServe.EXE running. OK to do?

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Mon, 14 Jul 2008 05:02:25 -0500

On Jul 13, 2008, at 19:37, Smith, Michelle wrote:

> Thanks for all responses. Rush - it would be great to keep the
> existing
> desktop that runs the SVNServe.exe as a service, but our IT guru's are
> trying to minimise the number of computers my group has (I have 3!)
> and
> will not allow us to keep this "mini-server" going. I think we're
> going
> to have to give the file:\\ method a go. I'm not concerned about the
> permissions, since this is a very small group so it should be easy
> enough to manage. I'll do some tests with multiple users commiting
> large files at the same time.

I strongly recommend you do not attempt to have multiple users
accessing a repository over the file:// protocol. It is not meant for
that. Please run svnserve or apache on a server. It does not have to
be a dedicated server; any computer you have that is on during the
times when the repository is to be accessed will probably be sufficient.

Though you can do yourself a favor now and define a new DNS alias for
that computer specifically for Subversion. So if your server's usual
address is henry.example.com, define a new DNS CNAME that points
svn.example.com to henry.example.com. Have everyone access your
repository using svn.example.com. That way if you later need to move
the repositories to a different server or to a dedicated server, you
won't have to inform anyone of a new address; you'll just have to
change the DNS alias.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-14 12:02:58 CEST

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.