Re: First-time user (Windows platform)

OK, let's do this one at a time:

> I'd recommend you start with storing your repo local to the server to get
> started. Get one thing working at a time.

That's what I'm doing for now. The only reason I mentioned the share
was to justify using the fileshare repo.

> It depends where you want the hook script to run: on the server or the
> client.

I need the hook to run on the server, so it can update the working
copy that is the dev environment.

> Yeah, unfortuantely, I understand completely. This is precisely the
> situation I was describing. Regardless, it's not clear if you have a
> distinct working copy from the "dev server" or not. Please clarify your
> working environment.

There are 4 zones within our environment, dev, test, staging and prod.
 The promotion from zone to zone is handled by a script (no human
intervention) which will also label the repo when I get this working.

Separate to this, I have a sandbox server, where I am playing with SVN
at the moment.

The repo will sit on the dev server, separate to the dev environment.

Ideally, the developers will not have direct access to the dev
environment at all, they will check out whatver files they need (to a
local folder), modify them (local copy), commit (hook script updates
dev version), and see the impact of their changes immediately on dev.
So dev will be a reflection of the HEAD version, and real "working"
working copies will be local for each developer.

Does that help? I'm not sure what details you need, so may be giving
too many, or the wrong ones :P

> Did you follow the specific instructions in the svn book for svnserve? For
> example, what do the following commands do, assuming the svn binaries are in
> your path?
>
> mkdir c:\tmp\svn
> svnadmin create c:\tmp\svn
> svnserve -d -r c:\tmp\svn

I used svnadmin to create my repo, so I know that works. and svnserve
with those parameters works too. When I run svnserve like that, it is
listening on port 3690, but when I run it through svnservice, it
listens on a random port, as I described before.

> You should be able to use either the svn client or TortoiseSVN to connect to
> svn://localhost and view the repo. You won't be able to make any changes
> though until you either add yourself to C:\tmp\svn\conf\passwd or enable
> anonymous changes in svnserve.conf.

I can't connect to svn:// at all, I get an "actively refused" message
(whether svnserve is listening on 3690 or another port). If I connect
through file:// it works fine. I have modified the authz and passwd
files, and for now * has rw access.

Authz looks like this:
[\]
admin = rw
* = rw

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 13 16:39:31 2006