vole
Clone
Read only, no credentials:
https://rodent.software/vole.git
Write over SSH with a registered key:
git clone ssh://git@rodent.software:2222/vole.git
A free and open-source forge that lives in your Git repo.
Document the root-level URL layout
b7396a1155147a13c5595216f204a545e9f74202 · Keenan Nemetz · 9h ago · parent ed03b3d1
Document the root-level URL layout The guides now say /<name> for a repository and /-/ for the forge's own pages, including the clone examples, theme asset paths, profile and registration URLs, robots.txt, and the deployment package URLs. docs/architecture.md gains a short URL layout section: why the two spaces cannot collide, the four root names the forge keeps, and why the transport carries .git. docs/go-modules.md follows the layout: the module path is the repository page, the clone URL is the same name with .git, discovery is answered before the router, and a published module path is durable because renaming the repository breaks it.
docs/deploy/digitalocean.md +2−2
| @@ -10,7 +10,7 @@ one DNS record. | |||
| 10 | 10 | - A DNS name, such as `forge.example.com`. | |
| 11 | 11 | - Your SSH public key. | |
| 12 | 12 | - The URL of a Vole `.deb` for `amd64`, from | |
| 13 | [Vole's releases](https://rodent.software/r/vole/releases). | ||
| 13 | [Vole's releases](https://rodent.software/vole/releases). | ||
| 14 | 14 | ||
| 15 | 15 | ## Render the first-boot file | |
| 16 | 16 | ||
| @@ -23,7 +23,7 @@ HOSTNAME=forge.example.com \ | |||
| 23 | 23 | ADMIN_ACCOUNT=admin \ | |
| 24 | 24 | ADMIN_EMAIL=you@example.com \ | |
| 25 | 25 | ADMIN_SSH_KEY="$(cat ~/.ssh/id_ed25519.pub)" \ | |
| 26 | VOLE_PACKAGE_URL=https://rodent.software/r/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb \ | ||
| 26 | VOLE_PACKAGE_URL=https://rodent.software/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb \ | ||
| 27 | 27 | ./render.sh > user-data.yaml | |
| 28 | 28 | ``` | |
| 29 | 29 | ||