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.
Rewrite the deployment guides as console walkthroughs
942c93cd06345416c580176c1a149f98e7e96cc0 · Keenan Nemetz · 3d ago · parent 51624dc6
Rewrite the deployment guides as console walkthroughs With the provider configurations gone, the guides are what is left, and their shape changed: render a file, paste it into a console field, point a name at the machine. The index gains the section the Terraform version did not need — first boot happens once. Editing the pasted file afterwards changes nothing, which is how cloud-init works rather than a limitation of these pages, so a later settings change is editing /etc/vole/vole.toml and restarting, and an upgrade is a package install. Each cloud page is a table of console fields: image, size, where the user data goes, and a firewall. The firewall table is load-bearing rather than advice, because Hetzner and DigitalOcean leave a new machine open and AWS hands it a security group that allows nothing inbound. The runner page leads with render.sh runner and keeps the by-hand path under it; the registration commands are written out now that no output prints them.
docs/deploy/docker.md +2−1
| @@ -109,7 +109,8 @@ point it at the instance: | |||
| 109 | 109 | vole runner --remote ssh://git@forge.example.com:2222 --container-runtime podman | |
| 110 | 110 | ``` | |
| 111 | 111 | ||
| 112 | See [Runners](../runner.md). | ||
| 112 | See [CI runners](runner.md) for the machine setup, and [Runners](../runner.md) for | ||
| 113 | every option. | ||
| 113 | 114 | ||
| 114 | 115 | ## Where the data is, and how to get it out | |
| 115 | 116 | ||