How Does Mercurial Communicate Changes Between Clients? -

I'm sorry if this question looks ridiculous, but I think it's a straightforward answer anywhere Can not find. .

I'm considering using Mercurial for source control over a small (2-3 developers) project, I do not know about subscribing to a central repository, and I like all that Has a complete copy of this project. What I do not understand is how the mercury clients make changes in each other. Does a particular port need to be opened or something similar?

Any indicators, which help for the commentary from Mercurial or those who have used it, will be received with gratitude.

Mercurial can reach remote repositories in many ways. The main types are:

• Use the file (i.e. see the repo on this path)
• HTTP / HTTPS (i.e. look at the repo at this web address)

The first really works only if your team has all the shared file system, But it is also useful if you have many clones that want to transfer information between you.

HTTP is how you can access a bitbasket or some other "Available to all" server You can set up a temporary server on a machine with the command hg service And this is useful if you have to share quickly with a colleague and do not care about security, but usually HTTP Merchant Server sits behind Apache or some other web server software.

An SSH based set-up is a machine running only one SSH server, which has Mercurial installed. Logs on the disorderly machine, and invokes hg from a distance. Then talk to the local hg and the remote hg link. In my opinion it is very easy to set up Certification All are handled in the normal SSH manner.

Read further: