~sircmpwn/sr.ht-docs

b6222a32dfc9e427f92a81bfdae8b3e0fc5ab156 — Drew DeVault 2 years ago e5c78ae
Fix old references to git-srht-* binaries
1 files changed, 7 insertions(+), 7 deletions(-)

M git.sr.ht/installation.md
M git.sr.ht/installation.md => git.sr.ht/installation.md +7 -7
@@ 21,11 21,11 @@ and ensure that the git.sr.ht web application runs as this user.
## SSH dispatch

It is necessary to configure git.sr.ht's SSH dispatcher as the system-wide SSH
authorization hook. In `/etc/ssh/sshd_config`, configure git-srht-dispatch like
authorization hook. In `/etc/ssh/sshd_config`, configure gitsrht-dispatch like
so:

```
AuthorizedKeysCommand=/usr/bin/git-srht-dispatch "%u" "%h" "%t" "%k"
AuthorizedKeysCommand=/usr/bin/gitsrht-dispatch "%u" "%h" "%t" "%k"
AuthorizedKeysCommandUser=root
PermitUserEnvironment SRHT_*
```


@@ 35,19 35,19 @@ obtain a list of authorized keys for the connecting user. The default behavior
is to read the `.ssh/authorized_keys` file from that user's HOME directory, but
the dispatcher can also "dispatch" to other authentication tools for other
users. This is used to authorize and perform git operations via the
`git-srht-keys` and `git-srht-shell`. See the `[dispatch]` section of your
`gitsrht-keys` and `gitsrht-shell`. See the `[dispatch]` section of your
git.sr.ht configuration for details on how this works and how to configure it
for additional services (e.g. man.sr.ht).

Authorization logs are written to `/var/log/git-srht-dispatch` and
`git-srht-shell`.
Authorization logs are written to `/var/log/gitsrht-dispatch` and
`gitsrht-shell`.

## Cronjobs

You must also configure `git-srht-periodic` to run periodically with your
You must also configure `gitsrht-periodic` to run periodically with your
favorite cron daemon. We recommend the following crontab:

    */20 * * * * git-srht-periodic
    */20 * * * * gitsrht-periodic

## HTTP(s) Cloning