README
changeset 100 db219a5a14f8
parent 83 86ec1268d306
child 101 8b4cdc066967
equal deleted inserted replaced
98:cacc2cf27d18 100:db219a5a14f8
    38 are authenticated only using SSH keys; no other form of authentication is
    38 are authenticated only using SSH keys; no other form of authentication is
    39 supported. 
    39 supported. 
    40 
    40 
    41 To give a user access to the repository, place their key in an
    41 To give a user access to the repository, place their key in an
    42 appropriately-named subdirectory of "/etc/mercurial-server/keys" and run
    42 appropriately-named subdirectory of "/etc/mercurial-server/keys" and run
    43 "/usr/local/lib/mercurial-server/refresh-auth". You can then control what
    43 "/usr/local/share/mercurial-server/refresh-auth". You can then control what
    44 access they have to what repositories by editing the control file
    44 access they have to what repositories by editing the control file
    45 "/etc/mercurial-server/access.conf", which can match the names of these keys
    45 "/etc/mercurial-server/access.conf", which can match the names of these keys
    46 against a glob pattern. 
    46 against a glob pattern. 
    47 
    47 
    48 For convenient remote control of access, you can instead (if you have the
    48 For convenient remote control of access, you can instead (if you have the
    73 Place your SSH public key in the directory "/etc/mercurial-server/keys/root".
    73 Place your SSH public key in the directory "/etc/mercurial-server/keys/root".
    74 I suggest creating yourself a directory and naming the key after your hostname
    74 I suggest creating yourself a directory and naming the key after your hostname
    75 (ie the file is called something like
    75 (ie the file is called something like
    76 "/etc/mercurial-server/keys/root/yourname/yourhostname") so that you can
    76 "/etc/mercurial-server/keys/root/yourname/yourhostname") so that you can
    77 easily manage users who have a different key on each host they use. Then run
    77 easily manage users who have a different key on each host they use. Then run
    78 "/usr/local/lib/mercurial-server/refresh-auth".
    78 "/usr/local/share/mercurial-server/refresh-auth".
    79 
    79 
    80 The repository is now ready to use, and you are now the sole user able to
    80 The repository is now ready to use, and you are now the sole user able to
    81 change and create repositories on this repository host.  
    81 change and create repositories on this repository host.  
    82 
    82 
    83 CREATING REPOSITORIES
    83 CREATING REPOSITORIES
    96 mercurial-server). You can add other root users by putting their keys next to
    96 mercurial-server). You can add other root users by putting their keys next to
    97 yours, or you can make less privileged users by putting their keys in the
    97 yours, or you can make less privileged users by putting their keys in the
    98 "keys/users" subdirectory - these users will be able to read and write to any
    98 "keys/users" subdirectory - these users will be able to read and write to any
    99 repository (except one - see below) but will not be able to create new
    99 repository (except one - see below) but will not be able to create new
   100 repositories. As always, when you change "/etc/mercurial-server/keys" you need
   100 repositories. As always, when you change "/etc/mercurial-server/keys" you need
   101 to re-run "/usr/local/lib/mercurial-server/refresh-auth".
   101 to re-run "/usr/local/share/mercurial-server/refresh-auth".
   102 
   102 
   103 LOGGING
   103 LOGGING
   104 
   104 
   105 Every push and pull is logged with the key used: see the file .hg/serve-log in
   105 Every push and pull is logged with the key used: see the file .hg/serve-log in
   106 each repository.
   106 each repository.