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/README.md +2−2
| @@ -24,9 +24,9 @@ nothing to install on your own computer except the shell you already have. | |||
| 24 | 24 | - **An SSH key.** It becomes the first account, and it is how you push. Any key | |
| 25 | 25 | you already use with another forge works. | |
| 26 | 26 | - **A package file.** Vole's releases are published on its own instance, at | |
| 27 | [rodent.software/r/vole/releases](https://rodent.software/r/vole/releases). Open | ||
| 27 | [rodent.software/vole/releases](https://rodent.software/vole/releases). Open | ||
| 28 | 28 | the release you want and copy the URL of the file for your machine's | |
| 29 | architecture: `…/r/vole/releases/<tag>/artifacts/vole_<version>-1_amd64.deb`, or | ||
| 29 | architecture: `…/vole/releases/<tag>/artifacts/vole_<version>-1_amd64.deb`, or | ||
| 30 | 30 | `arm64` instead of `amd64`. | |
| 31 | 31 | ||
| 32 | 32 | There is no container image. Vole is one process whose state is a directory on | |