You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by John Abraham <ja...@ucalgary.ca> on 2007/08/24 23:39:26 UTC
svnserve on two ports? Two svnserves?
I have Subversion nicely humming along on one port (the default) for
some users on one project, but I find that other users (on another
project) can't connect to that port because of corporate firewall issues.
I'd like to keep the old clients on the regular subversion port, but
experiment with having svnserve listen on another port (perhaps 81) for
the poor clients who have to live behind a firewall with a
non-cooperative IT department.
It doesn't look like there's a way to have svnserve listen on two
ports. Can I setup two instances of svnserve?
If not, could I set up Apache to listen through different ports? Can I
have apache and svnserve, each on different ports?
Ideally the one port would only go to one repository, and the other
would only go to the other.
Also, is there any easy way to see if the port is blocked or whether the
protocol (WebDAV, right?) is blocked? Because if the protocol is
blocked it's not much use trying out different ports.
I suppose an alternative is to run one on a completely separate machine,
but that seems like a pain.
Thanks In Advance,
--
John Abraham
jabraham@ucalgary.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnserve on two ports? Two svnserves?
Posted by Eric Hanchrow <of...@blarg.net>.
>>>>> "John" == John Abraham <ja...@ucalgary.ca> writes:
John> Can I setup two instances of svnserve?
This is uninformed speculation, but: I suspect you can, as long as
they run with the same userID. (My reasoning is: it's perfectly fine
for multiple processes to hit one repo when people are using file://,
so I can't see why multiple svnserve processes can't also hit it).
John> Can I have apache and svnserve, each on different ports?
I think that's also done occasionally. It's trickier, though, since
you'll have to arrange the permissions so that both apache _and_
svnserve have read and write access.
John> Ideally the one port would only go to one repository, and
John> the other would only go to the other.
Oh, two separate repositories? Then there's nothing to it; just do
it.
--
There is such a thing as American-ness. ... [H]ackers ... come
closest of any group I know to embodying it. Closer, probably, than
the men running our government.
-- Paul Graham
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org