rob thijssen
dff283c468
Builds crates/remote/Dockerfile from our mirror at git.lair.cafe rather than from GitHub, and resolves the version from the mirror's tags rather than GitHub's releases API. BloopAI has announced a sunset; the mirror exists so this build outlives them, which is pointless if the build still asks github.com what to build. Nothing in this image's path touches GitHub. Gitea mirrors carry tags but not releases, so latest is resolved by filtering to the strict release pattern v<semver>-<14-digit datestamp> and sorting on the datestamp -- which also skips the malformed historical tags in the upstream repo (vv.20250708094151, vv0.0.40-nbump.2....). FEATURES is deliberately left unset: the Dockerfile strips the private billing crate only when it is empty, which is the documented self-host path. Setting it would send the build looking for BloopAI/vibe-kanban-private over SSH, which we cannot reach. Consumed by the vibe-kanban quadlets on bob (kanban.internal). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TsmUEtbyTkgQ18tCFYXo1h
2.8 KiB
vibe-kanban-remote
The remote-server from vibe-kanban —
the self-hostable server half of the suite. Published as
git.lair.cafe/lair/vibe-kanban-remote:{version,latest}.
What it is
A single Rust binary (/usr/local/bin/remote) serving both an API and the built
remote-web SPA from /srv/static, listening on :8081 as uid 10001. Upstream
ships the Dockerfile (crates/remote/Dockerfile, context = repo root), so nothing
is vendored here — build.sh and the workflow build straight from that.
Built from our mirror, deliberately
Unlike hermes, this builds from git.lair.cafe/BloopAI/vibe-kanban, not
GitHub, and resolves its version from the mirror's tags rather than GitHub's
releases API.
BloopAI has announced a sunset. The mirror exists so this suite survives upstream going away, which is worthless if the build still calls GitHub to find out what to build. Nothing in this image's build path touches github.com.
Gitea mirrors carry tags but not GitHub releases, so "latest" is resolved by
filtering tags to the strict release pattern v<semver>-<14-digit datestamp> and
sorting on the datestamp. The filter also excludes malformed historical tags in the
upstream repo (vv.20250708094151, vv0.0.40-nbump.2.…) that would otherwise sort
unpredictably.
No private access required
crates/remote/Cargo.toml declares a billing dependency on the private
BloopAI/vibe-kanban-private repo. The Dockerfile deliberately strips it — and
deletes crates/remote/Cargo.lock — whenever the FEATURES build arg is empty,
which is the documented self-host path. Never set FEATURES; we have no access
to that repo and the build would fail trying to reach it over SSH.
Build args
| Arg | Value here | Why |
|---|---|---|
FEATURES |
(unset) | Strips the private billing crate. Setting it breaks the build. |
VITE_RELAY_API_BASE_URL |
(empty) | Baked into the SPA at build time; empty disables relay/tunnel, which we don't deploy. Changing it needs a rebuild, not a restart. |
Runtime
Consumed by the vibe-kanban quadlets on bob (kanban.internal). Needs a
PostgreSQL with wal_level=logical and an ElectricSQL sync service alongside;
SERVER_DATABASE_URL, ELECTRIC_URL and VIBEKANBAN_REMOTE_JWT_SECRET are
mandatory, and at least one auth provider must be configured or the server refuses
to start. It runs its own sqlx migrations on startup.
Note ElectricSQL cannot use client-certificate auth to Postgres, which is why this deployment runs its own Postgres rather than using magrathea's mTLS-only instance.
Local build
./build.sh # latest tag from the mirror
VK_REF=v0.1.44-20260424091429 ./build.sh # a specific tag