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.

Point the install instructions at rodent.software

c1edfd3c7d2d54c14e2b94405ca02232ba8e27da · Keenan Nemetz · 3d ago · parent 942c93cd

Point the install instructions at rodent.software

Vole's releases are now published on its own instance, so the guides name
that host instead of the placeholder: the .deb URL in each guide, the curl
in the manual install, and the release page where a reader finds both.

The example instance host stays forge.example.com, and stays distinct from
the host the package comes from. It stands for the reader's machine; calling
it rodent.software would invite someone to deploy their own forge under
someone else's name.

The sample in check-deploy.py moves with the guides, so the rendered user
data it checks carries a URL with the shape a real one has.

docs/deploy/aws.md +3−2

@@ -11,7 +11,8 @@ is not optional here.
11 11 - A DNS name, such as `forge.example.com`.
12 12 - An SSH key pair. The public half goes in the launch form and in the file; keep
13 13 the private half where you keep keys.
14 - The URL of a Vole `.deb` for `amd64`.
14 - The URL of a Vole `.deb` for `amd64`, from
15 [Vole's releases](https://rodent.software/r/vole/releases).
15 16
16 17 ## Render the first-boot file
17 18
@@ -24,7 +25,7 @@ HOSTNAME=forge.example.com \
24 25 ADMIN_ACCOUNT=admin \
25 26 ADMIN_EMAIL=you@example.com \
26 27 ADMIN_SSH_KEY="$(cat ~/.ssh/id_ed25519.pub)" \
27 VOLE_PACKAGE_URL=https://example.com/r/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb \
28 VOLE_PACKAGE_URL=https://rodent.software/r/vole/releases/v0.2.0/artifacts/vole_0.2.0-1_amd64.deb \
28 29 ./render.sh > user-data.yaml
29 30 ```
30 31