Since nobody has answered you yet (I was expecting a torrent of replies
actually), allow me:
Curtis Dunn wrote:
> I am not much of a network guy but I realize that we will have to
> install subversion to the main server. However, we want the appropriate
> engineers to be able to access the repository from anywhere on the local
> network. It would seem that installing subversion just to the server
> would be sufficient for allowing the engineers to access the repository
> through a terminal
I'm not quite sure what you're saying here. For a full, useful
subversion setup you need a server and one or more client(s).
> but since we are running windows I would like to try
> TortoiseSVN. I wouldn't think it would be necessary to install
> tortoisesvn to a user's computer in order for them to become a client,
They need to install some form of client, be it tsvn, the command line
svn client or another one. In your case, stick with tortoise svn (for
the users). So yes, you *do* need to install tortoisesvn to every user's
computer. (I'm not quite sure what line of thinking would lead you to
even consider that this wouldn't be necessary - I think it stems from a
fundamental misunderstanding of what subversion and tortoisesvn are).
> but I do not see how the user would be able to utilize the shell
> extension that allows them to control Subversion from within windows
That exactly *is* tortoisesvn.
> I guess what I am really trying to figure out is how to
> install Subversion with TortoiseSVN so that any computer on the network
> can be a client that has access to the repository.
Install the server software on a central machine and tortoisesvn on
every user's machine.
> Also I realize that Subversion can run with either a recent version of
> the apache web server or just with the standalone svnserve client. I
> believe it would be wise to start out with svnServe just to get the feel
> of Subversion.
No, not wise. You'd have to spend time now to get it working with
svnserve and then spend time later, while you've already set up a bunch
of stuff, to migrate to an apache setup. Start with an apache
installation from the get-go. Will you install the server on Windows or
> However, I am interested in some of the features that
> are only available with apache such as a web interface. Unfortunately,
> they state that subversion is "somewhat" slower with apache than it is
> with svnserve. Is apache a significantly slower option or is there only
> a minor change?
If you're installing on a P2/400 mhz with 64 mb of RAM, there's a
significant difference (this is not as uncommon as it would look -
shared hosts in the form of vps's often run in memory-constrained
environments). If you'll be installing on modern hardware the speed
difference is nothing to be worried about, especially considering the
extra's you get from using apache.
> Thanks in advance, and I apologize for the tedious "beginner level"
> questions as well as the long message.
It seems to me that you need a firm grasp of fundamental concepts of
version control with subversion first. Please buy / download 'Pragmatic
Version Control' (see
chapters 1-3 and appendix A (those are the chapters of the 1st edition
as I only have that one, you'd have to check if those chapters in the
2nd edition still correspond to those in the 1st). You'll have a
conceptual understanding of svn (if you read carefully) and then you'll
be ready to set up your own server, get some experience with the client
(install several clients: the command line clients and tsvn) and advance
to other topics.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 10 10:06:58 2007