Rob Brandt wrote:
> svn --newbie
> I have svn up and running on my debian server, using tortoise-svn on
> XP workstations.
> I would like to set up something that would "publish" HEAD to a web
> root directory on each commit. This is a development server, not
> "live". I've been reading the docs and it seems like it should be
> straightforward, but I just starting looking at the command line
> arguments and I can't think through how this is going to work.
> Specifically, permissions. My projects need to be password
> protected, and the "published" files need to have the right
> user/group permissions on the server.
Have you checked the FAQ?
Use that as a starting point. Changing permissions, if need be, should
be a straightforward modification of the code.
> I have been fooling around with the command line client, and I can get
> checkouts/updates to work via http://, but not file://. I'm using
> AuthType: Basic. Doing a checkout/update as root works, but the
> files then are owned by user/group root. I see that there are
> switches for username/password in checkout/update, but that seems to
> be for svn authorization, not system user assignment.
> Can someone point me in the right direction, or tell me I'm barking
> up the wrong tree?
I think you're doing some erroneous barking. Generally, you'll want one
access method to the repository, whether that's file:/// (note the third
slash), http://, svn://, or svn+ssh://. Since you mention http://
working, you probably want to use that method globally. (At a guess,
the repository is owned by the apache user (nobody), and no one else has
read access to the files; that's why you can only access the repository
as root using file:///, which is pretty much as expected.)
> Lastly, it occurs to me that on the live server I can install svn as
> well, and when I want to update the live server I can just svn update
> that as well, and it will be sync'ed with trunk effectively. Is that
> a reasonable thing, or are there gotchas that I'm not seeing?
Yep, that's pretty much exactly what you'll want.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Nov 8 19:45:35 2005