blob: c14c82c3bb542e3d8a8aab18920008b7f98e8dc8 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
---
title: hg.sr.ht Configuration
---
This document covers the configuration process for hg.sr.ht.
# Cronjobs
- `hgsrht-periodic`: The recommended configuration is
`*/20 * * * * hgsrht-periodic`.
- `hgsrht-clonebundles` (optional): It is recommend to run this job daily.
# Storage
## Repository
<div class="alert alert-info">
<strong>Note:</strong> If hg.sr.ht was installed in a package, you may skip
this section.
</div>
As a repository hosting service, hg.sr.ht requires a place for storing
repositories (we recommend `/var/lib/mercurial/`). It also requires a
`hg` user who has ownership over the repository storage location.
# SSH Dispatch
At the moment, hg.sr.ht uses git.sr.ht's SSH dispatcher, which you need to set
up as the system-wide SSH authorization hook. See git.sr.ht's [Configuration
page](/git.sr.ht/configuration.md) for more information.
Once this is done, you need to make the hg.sr.ht authorization hook be part of
the SSH dispatching, via the `hgsrht-keys` and `hgsrht-shell` scripts. See the
`[dispatch]` section of your hg.sr.ht configuration for more details.
Authorization logs are written to `hg-srht-shell`.
# HTTP(S) Cloning
hg.sr.ht does not do HTTP(S) cloning for you, so you'll need to set it up
yourself in Nginx. Here's an example Nginx configuration:
```nginx
location = /authorize {
proxy_pass http://127.0.0.1:5010;
proxy_pass_request_body off;
proxy_set_header Content-Length "";
proxy_set_header X-Original-URI $request_uri;
}
location ~ ^/[~^][a-z0-9_]+/[a-zA-Z0-9_.-]+/\.hg.*$ {
auth_request /authorize;
root /var/lib/mercurial;
}
```
It is important that you set up the `/authorize` endpoint to enforce the
privacy of private repositories.
|
