I'd vote against using svn+ssh without reason. I have setup this in our
environment here and can say that it is *a lot* slower than plain svn
(this is due to architectural reasons: each svn command is tunneled
through SSH and causes an svnservice command to be executed).
Yes, you no longer need the svnserve service. But instead of this you
need an SSH implementation for your OS which, for Windows, in most
cases also means a new service to be maintained, so you are back to
square one in your struggle with the admins.
On Linux/Un*x the scenario is different because many distros ship with an
SSH server daemon preconfigured, so you don't have to introduce a new
daemon.
Robert
> -----Original Message-----
> From: Rick Yorgason [mailto:rick@ldagames.com]
> Sent: Mittwoch, 6. Juni 2007 10:03
> To: Fournier,Danny [NCR]
> Cc: users@subversion.tigris.org
> Subject: Re: RE: http vs file
>
>
> Fournier,Danny [NCR] wrote:
> > What's a guy to do in a corporate environment where getting Apache or
> > SVNServe installed is impossible?
>
> Is getting svnserve impossible, or just running a daemon and opening up
> port 3690?
>
> It's been a while since I've dealt with svnserve, but if I recall, if
> you have ssh accounts to a machine then you don't have to have a server
> running or anything, you just need the svnserve *executable* installed
> somewhere on the machine visible from your PATH, and you can access
> svnserve over the svn+ssh protocol.
>
> Cheers,
>
> -Rick-
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 6 15:36:03 2007