My experiences with Mercurial

[Satish Balay]

On Sun, 17 Jun 2007, Milen Dzhumerov wrote:

> So really what we need is a simple & secure way for the users
> (developers in this case) to share their changesets.

> We're going back to using subversion because it's much easier for us
> to set up the central server once instead of setting up each client
> to act as a server/client.

This logic doesn't make sense to me. Whatever solution you came up for
svn - the same can be done with mercurial. [mercurial also offers many
alternative modes of sharing - but you don't have to use these
alternatives]

The 'simlpe & secure way' I would sugest for mercurial is:

- create a unix account for this project [on a machine accessiable via
ssh by all developers, and has mercurial installed]

- add every developers ssh public keys in this accounts's
~/.ssh/authorized_keys file [so they have read/write access to this
account]

- have a shared repostiotry hosted on this account - say at
/home/hg-repo/project and every developer uses the url:

ssh://projectname@machine//home/hg-repo/project

i.e each person shouldn't have to run their own ssh server. They all
access the shared repo via ssh client. Note: its possible to restrict
users from geting shell access on this project account - and only
access it via 'hg commands'
http://www.selenic.com/mercurial/wiki/index.cgi/SharedSSH

Satish