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.
Point the install instructions at rodent.software
c1edfd3c7d2d54c14e2b94405ca02232ba8e27da · Keenan Nemetz · 3d ago · parent 942c93cd
Point the install instructions at rodent.software Vole's releases are now published on its own instance, so the guides name that host instead of the placeholder: the .deb URL in each guide, the curl in the manual install, and the release page where a reader finds both. The example instance host stays forge.example.com, and stays distinct from the host the package comes from. It stands for the reader's machine; calling it rodent.software would invite someone to deploy their own forge under someone else's name. The sample in check-deploy.py moves with the guides, so the rendered user data it checks carries a URL with the shape a real one has.
docs/deploy/digitalocean.md +3−2
| @@ -9,7 +9,8 @@ one DNS record. | |||
| 9 | 9 | - A DigitalOcean account. | |
| 10 | 10 | - A DNS name, such as `forge.example.com`. | |
| 11 | 11 | - Your SSH public key. | |
| 12 | - The URL of a Vole `.deb` for `amd64`. | ||
| 12 | - The URL of a Vole `.deb` for `amd64`, from | ||
| 13 | [Vole's releases](https://rodent.software/r/vole/releases). | ||
| 13 | 14 | ||
| 14 | 15 | ## Render the first-boot file | |
| 15 | 16 | ||
| @@ -22,7 +23,7 @@ HOSTNAME=forge.example.com \ | |||
| 22 | 23 | ADMIN_ACCOUNT=admin \ | |
| 23 | 24 | ADMIN_EMAIL=you@example.com \ | |
| 24 | 25 | ADMIN_SSH_KEY="$(cat ~/.ssh/id_ed25519.pub)" \ | |
| 25 | VOLE_PACKAGE_URL=https://example.com/r/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb \ | ||
| 26 | VOLE_PACKAGE_URL=https://rodent.software/r/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb \ | ||
| 26 | 27 | ./render.sh > user-data.yaml | |
| 27 | 28 | ``` | |
| 28 | 29 | ||