Skip to content

Self-hosted Docker deploy: move Krater off weft behind a Cloudflare Tunnel - #100

Draft
Adambomb210 wants to merge 1 commit into
mainfrom
claude/selfhost-box
Draft

Adambomb210 wants to merge 1 commit into
mainfrom
claude/selfhost-box

Conversation

@Adambomb210

Copy link
Copy Markdown
Collaborator

Prep for moving Krater production (later staging) off weft onto one Ubuntu box with Docker, reached through a Cloudflare Tunnel. Nothing deploys from this PR: it adds deploy/selfhost/ (compose, follow timer, cutover README) and a pointer from docs/dev/production.md. See the commit message for details and what was tested locally; the follow script end to end, the tunnel and the real box are not tested yet.

🤖 Generated with Claude Code

… Cloudflare Tunnel

weft's internet and DNS drop out (2026-11-19 18:06Z), and every drop stalls the scheduler and running boxes'
reports. deploy/selfhost/ runs the same containers on any Ubuntu box with Docker:

- compose.yml: CI's image of one commit (no builds), Postgres 18 (skein's version) with the restored `krater`
  schema, SeaweedFS 4.47 with a volume cap, cloudflared, a daily dump; data in bind mounts under KRATER_DIR.
  migrate keeps weft's rule that an older release on a newer database starts without migrating.
- krater-follow + systemd timer: deploys the production branch like krater-prod-follow (on main, all checks
  green, dump first, health by revision, falls back to the previous release).
- README: the box, what Jasper hands over, a compute-off dry run, a store pre-copy with rclone, the cutover
  order (weft's scheduler stops before the final dump: one scheduler per label prefix), DNS, checks, going back,
  and staging.

Tested locally on Docker Desktop: the stack at 44c346c answers /healthz and /healthz/worker; a --schema=krater
dump of a skein-like patchwork_central restores into the box's db and migrate finds nothing to do.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant