Sign in

Search issue titles and bodies, change requests and comments. Private repositories you cannot read are not included.

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 the root-level URL layout

b7396a1155147a13c5595216f204a545e9f74202 · Keenan Nemetz · 2h ago · parent ed03b3d1

Document the root-level URL layout

The guides now say /<name> for a repository and /-/ for the forge's own pages,
including the clone examples, theme asset paths, profile and registration
URLs, robots.txt, and the deployment package URLs. docs/architecture.md gains
a short URL layout section: why the two spaces cannot collide, the four root
names the forge keeps, and why the transport carries .git.

docs/go-modules.md follows the layout: the module path is the repository page,
the clone URL is the same name with .git, discovery is answered before the
router, and a published module path is durable because renaming the repository
breaks it.

docs/README.md +3−2

@@ -54,8 +54,9 @@ Use one word for each concept, in the interface and the guides:
54 54 - **account**: the identity that owns keys, passkeys, sessions, and roles. The CLI
55 55 spells its commands `vole admin account ...`; `vole admin user ...` remains as
56 56 an alias. The database file is `data/users.db`; in prose it is still an account.
57 - **repository**: the Git repository and what belongs to it. The CLI uses `repo`
58 and URLs use `/r/<name>`; do not call it a project.
57 - **repository**: the Git repository and what belongs to it. The CLI uses `repo`,
58 URLs use `/<name>`, and the forge's own pages live under `/-/`; do not call it a
59 project.
59 60 - **change request**: a proposed branch reviewed before landing. The CLI uses
60 61 `change` and the route is `/changes`.
61 62 - **enrollment link**: the one-time link that lets someone register a passkey and