equal
deleted
inserted
replaced
121 remote: adding file changes |
121 remote: adding file changes |
122 remote: added 1 changesets with 1 changes to 1 files |
122 remote: added 1 changesets with 1 changes to 1 files |
123 jay@my-workstation:~/hgadmin$ </computeroutput></screen> |
123 jay@my-workstation:~/hgadmin$ </computeroutput></screen> |
124 <para> |
124 <para> |
125 Sam can now read and write to your |
125 Sam can now read and write to your |
126 <literal>ssh://hg@repository-host/repository/name</literal> repository. |
126 <uri>ssh://hg@repository-host/repository/name</uri> repository. |
127 Most other changes to access control can be made simply by making and |
127 Most other changes to access control can be made simply by making and |
128 pushing changes to <filename |
128 pushing changes to <filename |
129 class='directory'>hgadmin</filename>, and you can use Mercurial to |
129 class='directory'>hgadmin</filename>, and you can use Mercurial to |
130 cooperate with other root users in the normal way. |
130 cooperate with other root users in the normal way. |
131 </para> |
131 </para> |
435 <title>How mercurial-server works</title> |
435 <title>How mercurial-server works</title> |
436 <para> |
436 <para> |
437 All of the repositories controlled by mercurial-server are owned by a |
437 All of the repositories controlled by mercurial-server are owned by a |
438 single user, the <systemitem |
438 single user, the <systemitem |
439 class="username">hg</systemitem> user, which is why all URLs for |
439 class="username">hg</systemitem> user, which is why all URLs for |
440 mercurial-server repositories start with <literal>ssh://hg@...</literal>. |
440 mercurial-server repositories start with <uri>ssh://hg@...</uri>. |
441 Each SSH key that has access to the repository has an entry in |
441 Each SSH key that has access to the repository has an entry in |
442 <filename>~hg/.ssh/authorized_keys</filename>; this is how the SSH daemon |
442 <filename>~hg/.ssh/authorized_keys</filename>; this is how the SSH daemon |
443 knows to give that key access. When the user connects over SSH, their |
443 knows to give that key access. When the user connects over SSH, their |
444 commands are run in a custom restricted shell; this shell knows which key |
444 commands are run in a custom restricted shell; this shell knows which key |
445 was used to connect, determines what the user is trying to do, checks the |
445 was used to connect, determines what the user is trying to do, checks the |