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.

Require an image for every CI job

70b702649b875d841e294f5a085ca784d43e5bc4 · Keenan Nemetz · 15d ago · parent 7da9111e

Require an image for every CI job

Runners now require an OCI runtime, and each workflow job must name either a registry image or an image-file definition under .vole/images. Definitions are validated at push time, pinned with the run, built locally by the runner, and cached by definition digest. Records and the run page carry the image and definition digest.

Split the CI guide into workflows and runners, and add reference pages for workflow and image definition fields.

docs/architecture.md +4−3

@@ -120,6 +120,7 @@ Vole is built for one team on one server. It does not support multiple tenants,
	120	120	federation, custom domains with automatic certificates, horizontal scaling, or a
	121	121	Kubernetes deployment story. These are not part of Vole today.
	122	122
	123		CI isolation is a runner decision rather than a workflow feature: the runner can
	124		execute each job in a container from an image the operator chooses, but Vole does
	125		not pull images, choose dependencies, or orchestrate containers from the server.
		123	CI isolation is a runner responsibility: every job names its OCI image in the
		124	workflow, or references a definition under `.vole/images`, and the runner executes
		125	it in a container. The runner pulls or builds the image and owns the container
		126	runtime; the server only pins the image and definition and records what ran.