vole
Clone
Read only, no credentials:
https://rodent.software/git/vole.git
Write over SSH with a registered key:
git clone ssh://git@0.0.0.0:2222/vole.git
A free and open-source forge that lives in your Git repo.
Add automatic HTTPS with ACME
642e599466fe4f5066afdc9a24775694a52c9749 · Keenan Nemetz · 14d ago · parent 91e6a33a
docs/sites.md +8−4
| @@ -61,10 +61,14 @@ branch name to `vole pages deploy --branch`. | |||
| 61 | 61 | - A private repository has no public website. There is no logged-in reader, so the | |
| 62 | 62 | site returns `404`, just like its clone URL. | |
| 63 | 63 | ||
| 64 | Sites use subdomains of the instance's own domain, so they can share the | ||
| 65 | certificate you already have. Terminate TLS in a proxy in front of `http_addr` and | ||
| 66 | keep the `Host` header; it is how Vole knows which site was requested. See | ||
| 67 | [Configuration § Running behind a proxy](configuration.md#running-behind-a-proxy). | ||
| 64 | With automatic HTTPS enabled (`https_addr`), Vole obtains a certificate for each | ||
| 65 | site host the first time it is requested, as long as the repository exists and is | ||
| 66 | publicly readable. A wildcard DNS record pointing at the instance is enough; | ||
| 67 | wildcard certificates are not supported, so each host is issued separately. Without `https_addr`, terminate | ||
| 68 | TLS in a proxy in front of `http_addr` and keep the `Host` header: it is how Vole | ||
| 69 | knows which site was requested. See | ||
| 70 | [Configuration § Automatic HTTPS with ACME](configuration.md#automatic-https-with-acme) | ||
| 71 | and [Configuration § Running behind a proxy](configuration.md#running-behind-a-proxy). | ||
| 68 | 72 | ||
| 69 | 73 | A workflow can publish the site as its last step. See | |
| 70 | 74 | [Workflows § Publish a website](workflows.md#publish-a-website). | |