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.

Document deploying to a server, one guide per path

b8e7a5679847cf4cdda0754f6154805585e1be96 · Keenan Nemetz · 3d ago · parent b86148d1

Document deploying to a server, one guide per path

The guides are for someone who has a machine and a domain and has not
deployed a forge before, so they start from what to have ready and end at a
working https address with one instance admin.

Each ends with the same three things: where first-boot output is, what a
certificate warning means, and that pushing needs port 2222 reachable and a
key that belongs to an account.

The index page carries what the per-cloud pages should not repeat: backups
are separate from a cloud snapshot because secrets.key must not travel with
the data, and upgrades are a package install rather than an apply.

docs/packaging.md +6

@@ -12,6 +12,12 @@ dnf install ./vole-0.2.0-1.x86_64.rpm # Fedora, RHEL, Rocky
	12	12	There is no apt or dnf repository and no signature on these files yet. Each release
	13	13	page also carries `SHA256SUMS`; compare it before installing.
	14	14
		15	To have a fresh cloud machine install and configure the package for you, use the
		16	[deployment guides](deploy/README.md). They need the URL of the file above, which
		17	is how a `.deb` from a release page is named:
		18	`.../r/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb`, or `arm64` for an
		19	`arm64` machine.
		20
	15	21	Both packages depend on `git` and the system SQLite library: `libsqlite3-0` on
	16	22	Debian and Ubuntu, `sqlite-libs` on Fedora, RHEL, and Rocky. Vole links SQLite
	17	23	dynamically, so the library must be present where the binary runs; the package