[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: http vs file

From: Matt Sickler <crazyfordynamite_at_gmail.com>
Date: 2007-06-05 17:16:35 CEST

file:/// = DONT
IMO you should only use file:// if you are the only one using the repo
and its only for testing something
either use apache + mod_dav_svn or svnserve - the latter probably being easier

On 6/5/07, Fournier,Danny [NCR] <Danny.Fournier@ec.gc.ca> wrote:
> I'm just wondering the pros and cons of using http vs file.
>
> So far, I've been using the file approach. That has been positive for me
> so far.
>
> However, I might start a project with a collegue that will need access
> to the repository remotely. We're using Hamachi to bridge our connection
> and we are able to share documents via shares on our PCs through the
> Hamachi connection.
>
> I was thinking creating a share on my webserver (Win2k3, IIS, SQL 2005),
> share the repository and dev folders and have him access them through
> Hamachi using the file approach. Another idea I read about was
> installing Apache on the webserver, having it run on a different port
> and have us access the repository that way.
>
> 1. Would using http make the Subversion process faster? Checkout,
> commits, ect...?
> 2. Is authorization the main attraction of using Apache for repository
> access (compared to using file)?
>
> Any insight (or link) would be appreciated. The best site I've found so
> far:
> http://svn.spears.at/
>
> Thanks,
>
> Dan
>
> ---------------------------------------------------------------------
> 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 Tue Jun 5 17:17:20 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.