Sharing the repository and having everyone run their own server
defeats the purpose. Not just with SVN but with any sepup where we
have a server process and a data store the pourpose of the server
mostly is to serialize or control access to the data, maintain locks
and so on.
On Thu, Sep 22, 2011 at 11:40 AM, David Weintraub <qazwart_at_gmail.com> wrote:
> One of the nice thing about Dropbox is that you can share files
> between various users. I will sometimes keep a Subversion repository
> on Dropbox, so I can access it on various systems. Right now, it's
> just for me to use.
>
> Here's the scenario:
>
> * I have my Dropbox under $HOME/Dropbox.
> * I create a Subversion repository on $HOME/Dropbox/svn_repos
> * I now share my $HOME/Dropbox/svn_repos folder between my colleagues.
>
> What happens if we all start svnserve on that particular shared folder
> in Dropbox? Is there an issue with possible collisions if two or more
> people attempt to commit their changes at the same time?
>
> What if we skip the svnserve route and merely use the file://
> protocol? Is this any safer?
>
> --
> David Weintraub
> qazwart_at_gmail.com
>
--
Chris Albertson
Redondo Beach, California
Received on 2011-09-22 20:48:17 CEST