On 10/13/06, Phyrefly <phyrefly.phyre@gmail.com> wrote:
>
>
> I am on a Windows network, and I am using a file system repository
> (not berkeley) as I need to put the repo on a network share. I have
> installed svnservice on the server, and am using TortoiseSVN as a
> client (although I've tried everything that's giving me problems as a
> command-line command as well).
If you're using svnserve, and you should be, you probably want the repo on
the server's local drive.
Firstly, I have a very large number of small projects, and I'm not
> sure if I should be creating a lot of repositories (high overhead when
> creating a project, but low when accessing the repos) or one big one
> (easy to add a project, but potentially a lot of overhead when
> updating). Does anyone have any advice on this for me?
Personally, I prefer creating a single repo since it's easier to administer
(backup, verify, dump/load are easier on a single repo) and permisions are
now flexible enough to allow fine-grained control. A single repo also means
the creation of a new project is very easy. Creating a whole new repo is
harder, requiring the intervention of an admin or script on the svn server.
Secondly, I need our development environment to stay up to date with
> the HEAD. I've realised I can do this with a post-commit.bat file -
> but I can't make this work. The bat file seems to run on the client,
> not the server (where both the repo and the dev environment sit). Is
> this as simple as a one-line svn update command? (assuming all the
> right users have the right permissions, of course) Is there any way
> to update only one projet within the repository (obviously there is,
> rather, is there a way of knowing which one has just been commited in
> the hook script?)
The hook script do run on the server when you access the repo using
svnservice but you're using file:// access so the server and client are the
same machine.
Are you certain you want a shared dev environement? As a developer, I hate
to use shared environements because I'm never sure when a problem is due to
my change or something Bob changed. And I would never want my dev
environement, shared or not, to be automatically updated without knowing
when or what was updated.
This may be a symptom of the next problem: namely, I can't seem to
> access the repo as a svn:// url, only as a file:// share. Even when
> attempting from the server itself (svn://localhost/) I get a
> connection "actively refused" error. However, the fileshare option
> works locally or across the network.
In my experience, this error is caused a software firewall running on the
server.
Good luck...
Kevin
Received on Fri Oct 13 14:11:20 2006