Repository on shared disk

[Adrian Buehlmann]

On 08.10.2009 10:10, Alexander Schatten wrote:
> Ok, sorry for the rookie question, but I really wanted to clearify that before I ruin my repository.

The only thing that ruins repositories are:

- users deleting repos or parts of it
- broken on-access-scanning virus scanners on Windows, breaking any sane assumptions about a
  filesystem API (Known troublemakers: Avira, AVG)
- bugs in software (including Mercurial, see the bugtracker)
- other fs defects like OS errors or hardware problems

Also, beware of the limitations of Mercurial mentioned in:

http://mercurial.selenic.com/wiki/HandlingLargeFiles

Mercurial will warn you when you try adding a large file.

> As I understand it, it is possible to put a Mercurial repository on a shared disk. Correct? Is Mercurial taking care of synchronisation/locking in case two clients try to write-access the repo?

Correct, provided the fs API works as expected.

Mercurial takes care to nicely get along with other instances
of itself running in other processes, accessing the same repo
(read and write).

It uses write lock files inside the repo to ensure
consistency.

DISCLAIMER:

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.