Accessing repository with svn vs. svn+ssh

[Rick Haller <rp...@dstsystems.com>]

I created a repository in /svnrepos.   The repository was populated with 
projects using cvs2svn.  
The filesystem is berkely-db.   We won't be using Apache, just svnserve.
I am able to checkout projects using svn: and svn+ssh: and commit 
changes.   However, there appears to be a discrepency between
the two protocols. 

To use svn: the command looks like     svn checkout 
svn://myserver/trunk/proj1
To use svn+ssh:  the cmd looks like     svn checkout 
svn+ssh://myserver/svnrepos/trunk/proj1

If I don't use the commands as shown above, I receive the following errors.
svn: URL 'svn://myserver/svnrepos/trunk/proj1' doesn't exist
svn: URL 'svn+ssh://myserver/trunk/proj1' doesn't exist

Can someone explain the difference and why ?    Is there a way to use 
the svn: protocol so that it includes "svnrepos" in the url ?

Thanks,
Rick
rphaller@dstsystems.com
-----------------------------------------
This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law.  If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender.  If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Accessing repository with svn vs. svn+ssh

[Ryan Schmidt <su...@ryandesign.com>]

On Jul 17, 2007, at 12:34, Rick Haller wrote:

> I created a repository in /svnrepos.   The repository was populated  
> with projects using cvs2svn.  The filesystem is berkely-db.   We  
> won't be using Apache, just svnserve.
> I am able to checkout projects using svn: and svn+ssh: and commit  
> changes.   However, there appears to be a discrepency between
> the two protocols.
> To use svn: the command looks like     svn checkout svn://myserver/ 
> trunk/proj1
> To use svn+ssh:  the cmd looks like     svn checkout svn+ssh:// 
> myserver/svnrepos/trunk/proj1
>
> If I don't use the commands as shown above, I receive the following  
> errors.
> svn: URL 'svn://myserver/svnrepos/trunk/proj1' doesn't exist
> svn: URL 'svn+ssh://myserver/trunk/proj1' doesn't exist
>
> Can someone explain the difference and why ?    Is there a way to  
> use the svn: protocol so that it includes "svnrepos" in the url ?

You have presumably started your svnserve (the one that's used for  
the svn:// protocol) using "svnserve -r /svnrepos". I think if you  
want to specify "svnrepos" as part of the URL, then you would use "- 
r /" or just omit the "-r" option.

It's probably a better idea, though, to restrict these URLs to just a  
directory in which you host your repositories. If you allow any  
directory on the server to be accessed, that might make it harder to  
keep any private repositories hidden.

So I recommend you start svnserve with some -r option, and also  
configure your svn+ssh:// to restrict users to the same root. See:

http://svnbook.red-bean.com/en/1.2/ 
svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org