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.
Manage accounts from the users directory, not the Admin tab
ea21f923d1fabe3a633e3dc4713ca18d211dbfcb · Keenan Nemetz · 4d ago · parent f11854fe
Manage accounts from the users directory, not the Admin tab The Accounts tab rendered every account in the roster, which costs more as an instance grows and duplicates a directory that is already paginated, searchable, filterable, and sortable. The tab now keeps the invite and bot forms and points at /u, and an instance admin gets a Manage action on each directory row that opens the account page. The Manage column is presentation only: the account page still checks the instance-admin role, so a non-admin who types its URL gets the usual 404. Refs #198 (01M6MK0NNZ2XR1D5TQKNWYT4HN).
docs/accounts-and-access.md +9−7
| @@ -247,13 +247,15 @@ and SSH LFS use the key's account for this check; anonymous HTTP clone has no | |||
| 247 | 247 | identity, so a private repository still answers `404` there. | |
| 248 | 248 | ||
| 249 | 249 | Instance admins also get an **Admin** page in the top navigation. Its tabs cover | |
| 250 | the instance's overview, storage, runners, and effective configuration; the | ||
| 251 | accounts roster, where an admin creates an account from an enrollment link, sets | ||
| 252 | its instance-wide role (including `admin`), retires an account, starts a fresh | ||
| 253 | enrollment link, and inspects or revokes SSH keys and browser sessions; and the | ||
| 254 | audit log. Repository creation is a **New repository** action on the home page, | ||
| 255 | and per-repository access rules live on that repository's **Settings** tab, | ||
| 256 | visible there to instance admins. | ||
| 250 | the instance's overview, storage, runners, and effective configuration; an | ||
| 251 | Accounts tab that creates a person from an enrollment link or an automation | ||
| 252 | account; and the audit log. Existing accounts are managed from the users | ||
| 253 | directory at `/u`, which is searchable and paginated: an instance admin gets a | ||
| 254 | **Manage** action on each row that opens the account page, where they set its | ||
| 255 | instance-wide role (including `admin`), retire it, start a fresh enrollment link, | ||
| 256 | and inspect or revoke SSH keys and browser sessions. Repository creation is a | ||
| 257 | **New repository** action on the home page, and per-repository access rules live | ||
| 258 | on that repository's **Settings** tab, visible there to instance admins. | ||
| 257 | 259 | ||
| 258 | 260 | The first instance admin must be granted on the host. Instance admin is the | |
| 259 | 261 | instance-wide `admin` role, so `vole admin account role alice admin` and | |