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/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.

Remove the container deployment

9bce37233413e6a56c38d5cf90e79dfa496649b2 · Keenan Nemetz · 3d ago · parent c1edfd3c

Remove the container deployment

A Vole instance is one process whose state is a directory on local disk. A
container therefore adds a layer without removing one, and it costs
something real: the service unit's hardening, and the CI half, which needs
an OCI runtime the container does not have without mounting the host's
socket — the thing the runner docs refuse.

It was also the weakest path in practice. No image is published, so an
upgrade meant a source checkout and a Go build where the package is one
`apt install`. CI never ran the container; it was tested by hand once, which
is a surface that rots quietly.

So the Dockerfile, the compose file, the entrypoint, the image's
configuration, and the guide go. The deployment checker loses its compose
and COPY checks, and the render script is the only shipped script left.

Every other mention of Docker in the repository means the CI container
runtime, and those stay.

Users who manage their machines with Compose or Kubernetes are told where
they stand: give the forge a small virtual machine of its own, and the
first-boot file works there unchanged.

deploy/docker/vole.toml −31

@@ -1,31 +0,0 @@
1 # The configuration the image starts with, and the file to copy and edit for a
2 # real deployment. Every setting is documented in docs/configuration.md.
3
4 data_dir = "/var/lib/vole/data"
5
6 # The web interface and anonymous clone. A container is reached through its
7 # published ports, so this listens on every address inside it; keep the published
8 # port on the host's loopback and let a TLS proxy be the only way in, or set
9 # https_addr below and publish 80 and 443 instead.
10 http_addr = "0.0.0.0:8080"
11
12 # Git over SSH, the only write transport.
13 ssh_addr = "0.0.0.0:2222"
14
15 # The address people reach this instance on. Passkey sign-in needs an https URL,
16 # so set it before anyone signs in: browsers bind a passkey to that address, and
17 # changing it later means re-enrolling everyone.
18 # public_url = "https://forge.example.com"
19
20 # Behind a proxy, name the header it sets with the client address. Without it the
21 # per-client clone limit and the sign-in rate limits see every request as coming
22 # from the proxy.
23 # git_http_client_ip_header = "X-Forwarded-For"
24
25 # Or let Vole obtain its own certificate, and put nothing in front. That needs
26 # ports 80 and 443 published, DNS pointing here, and public_url set.
27 # https_addr = ":443"
28 # http_addr = ":80"
29 # acme_email = "admin@example.com"
30
31 # instance_name = "Vole"