> If you're using svnserve, and you should be, you probably want the repo on
> the server's local drive.
I am trying to use it, yes. But the server's data drives (although
mapped) are not local to the server (on our actual dev environment,
where I am at the moment (sandbox server) it's all one machine, but I
can't even get it working here!)
> 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.
This was my gut feel, just looking for some confirmation :).
> 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.
I can use file:// successfully across the network too
(file://IP.Address/folder). This runs the hook script on my pc, not
my sandbox server. Will this not be a problem when I get svn:/// to
> 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.
I have no choice, unfortunately. Because it's a web project (or more
accurately collection of projects) - and management won't let us run
IIS on our local machines, we need to put the changes on the dev
server to see the result. So there will be people doing HTML/design
work, then I'll pick it up and do the ASP bits, then give it back for
them to neaten up the look and feel again. Conflicts and/or
"who-broke-what" situations aren't a big problem, but the environment
does need to be kept up to date. This is why we want Subversion, so
at least I can say "no, you've deleted all my code" and roll-back,
rather than having to do it all again.
> In my experience, this error is caused a software firewall running on the
No good... there's no software firewall running (and I'm trying to
connect from the local machine as well as from my PC, and neither
Anybody else have any ideas? And for that matter, how to get svnserve
to run on the right port?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Oct 13 14:40:37 2006