vole

Clone

Read only, no credentials:

https://rodent.software/vole.git

Write over SSH with a registered key:

git clone ssh://git@rodent.software:2222/vole.git

A free and open-source forge that lives in your Git repo.

Simplify the home page around the instance introduction

ff9870f1a26a17d54c21d411000a6c7d58ab5c0d · Keenan Nemetz · 1d ago · parent 6ce635a8

Simplify the home page around the instance introduction

Drop the page header and its hero actions. The instance name and sign-in links already live in the top bar, and the introduction is the place to say what the forge is. Move New repository into the Repositories heading, where it sits with the list it creates.

Remove the introduction card header and its in-page editor. The introduction is profile/README.md in the instance repository, so it is read and pushed like every other customization. The POST / handler and its editor code go with it; an instance admin without an instance repository still gets the setup hint.

docs/operations.md +3−3

@@ -185,9 +185,9 @@ it cannot restore CI history.
	185	185	- The web interface is read-only for anonymous visitors. Passkey sign-in enables
	186	186	issue, comment, and approval writes; HTTP Git clone remains read-only. There is
	187	187	no password store. Restoring an old `users.db` should be followed by
	188		`vole admin account revoke-sessions --all`. The landing page's introduction is
	189		the exception: an instance admin can edit it on the home page, but the save is
	190		a commit to the instance repository (`instance_repo`), and it is audited.
		188	`vole admin account revoke-sessions --all`. The landing page introduction is
		189	not an exception: it is `profile/README.md` in the instance repository
		190	(`instance_repo`), edited by pushing like every other customization.
	191	191	- Account names are permanent. They name contributor branches, so an upgrade from
	192	192	a build where names could change keeps each account's current name and forgets
	193	193	the former ones.