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 to
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 LAN
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.) Other
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 one).
Those urls all point to the same place in my file system, including any
repositories there.
QUESTIONS:
- As far as TortoiseSVN etc is concerned, none of them are the same, right?
If I check out files using localhost, tortoise knows where they came from,
and I need to check them back in to localhost too, right? Not to any of the
other equivalent urls?
- Will it cause problems if I check things out from localhost, and other
people check things out from my WAN ip? Are we ok as long as we each are
independently consistent about the urls we use?
I hope so, because none of the urls I can use when I'm portable and off
the net can be used by other people when I'm connected and on the net.
- 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 may
change, if that's avoidable.)
Thanks, hope this is clear,
Dave Merrill
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 23 20:25:17 2005