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/README.md +4−3

@@ -24,9 +24,10 @@ nothing to install on your own computer except the shell you already have.
	24	24	pick the name you intend to keep.
	25	25	- An SSH key. It becomes the first account, and it is how you push. Any key
	26	26	you already use with another forge works.
	27		- A package file. Vole is distributed as a `.deb` (and `.rpm`) attached to a
	28		release. Copy the URL of the file for your machine's architecture: recent
	29		releases are `…/releases/<tag>/artifacts/vole_<version>-1_amd64.deb`, or
		27	- A package file. Vole's releases are published on its own instance, at
		28	[rodent.software/r/vole/releases](https://rodent.software/r/vole/releases). Open
		29	the release you want and copy the URL of the file for your machine's
		30	architecture: `…/r/vole/releases/<tag>/artifacts/vole_<version>-1_amd64.deb`, or
	30	31	`arm64` instead of `amd64`.
	31	32
	32	33	## What happens on first boot