On 23.05.2005, at 20:23, Dave Merrill wrote:
> Getting started w svn, I've set up some repositories on my laptop,
> accessible only through apache. I'll be using them myself, and I want
> make it possible for collaborators to use them too.
> I'm trying to understand the effect of the different possible urls
> that all
> point to the same repository. I need to figure out which one(s) to use
> myself, which to give to others, and whether apache should be
> configured to
> only allow some of them to be used.
> From my own machine, I can use urls starting with my machine name, my
> ip, my WAN ip (if the firewall allows it), localhost, or 127.0.0.1. (No
> domain name points here, but if it did, it would act like my WAN ip.)
> users on the LAN could use any of those except localhost and
> 127.0.0.1, and
> users off the LAN could use only my WAN ip (or domain if there was
> Those urls all point to the same place in my file system, including any
> repositories there.
> - As far as TortoiseSVN etc is concerned, none of them are the same,
> If I check out files using localhost, tortoise knows where they came
> and I need to check them back in to localhost too, right? Not to any
> of the
> other equivalent urls?
When you do a checkout from any URL, that URL is written into (the .svn
directories in) the new working copy. In the future when you update
that working copy or check files in from that working copy, you do not
specify a URL of the repository -- Subversion already knows the URL
because it's encoded in the working copy. If you later want to change
the URL of the repository with which the working copy is associated --
provided it is merely a different URL to access the same repository,
and not in fact a different repository -- you issue an "svn switch
> - Will it cause problems if I check things out from localhost, and
> people check things out from my WAN ip? Are we ok as long as we each
> independently consistent about the urls we use?
> I hope so, because none of the urls I can use when I'm portable and
> the net can be used by other people when I'm connected and on the net.
It is no problem to have multiple URLs that refer to the same
repository, or to have these used by one or more people.
But it doesn't sound like a very good idea to try to host a repository
on your laptop when others will want to access it. You should instead
set up the repository on a central server that can always be online. If
you'd like to have a copy of the repository on your laptop for working
with when you're away from the central server, I understand that SVK
can help: http://svk.elixus.org/
> - Is there anything else I should be thinking about in this area? Any
> reasons for picking one over another? (Other than not using ips that
> change, if that's avoidable.)
As with any server, pick an address that you can stick with. If you
change the URL later, you'll have to inform your users of the change.
How big of a hassle that is depends on how many people use it.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon May 23 23:04:58 2005