starred/warmbly

mirror of https://github.com/warmbly/warmbly.git synced 2026-09-05 16:02:48 +00:00

Files

T

History

Matthew Meszaros bb35de0455 feat: address review on self-hosted updates: the updater no longer re-locks its mutex when a job finishes (every job used to deadlock at completion and freeze the status API), the backend caches the updater view so the member version pill, the health checks and the admin poll share one read and an absent updater is reported as not running rather than broken, the bare-metal upgrade builds unprivileged and hands off to a root-owned fixed-path installer that refuses symlinks so sudoers allows one command instead of install/cp/rm/chown/chmod/systemctl/ln, the installer fails when the backend does not come back, the seed image gets the version build args, the dashboard gates the update action on manage_settings and stops polling a backend that answers 404, and revived timestamps are typed as Date

2026-09-03 05:04:30 -07:00

..

README.md

feat: address review on self-hosted updates: the updater no longer re-locks its mutex when a job finishes (every job used to deadlock at completion and freeze the status API), the backend caches the updater view so the member version pill, the health checks and the admin poll share one read and an absent updater is reported as not running rather than broken, the bare-metal upgrade builds unprivileged and hands off to a root-owned fixed-path installer that refuses symlinks so sudoers allows one command instead of install/cp/rm/chown/chmod/systemctl/ln, the installer fails when the backend does not come back, the seed image gets the version build args, the dashboard gates the update action on manage_settings and stops polling a backend that answers 404, and revived timestamps are typed as Date

2026-09-03 05:04:30 -07:00

warmbly-backend.service

feat: add deploy/systemd units for backend, consumer, worker, tracking and realtime so a Docker-free install runs every service as the unprivileged warmbly user from /opt/warmbly with EnvironmentFile config

2026-08-29 23:37:22 -07:00

warmbly-consumer.service

feat: add deploy/systemd units for backend, consumer, worker, tracking and realtime so a Docker-free install runs every service as the unprivileged warmbly user from /opt/warmbly with EnvironmentFile config

2026-08-29 23:37:22 -07:00

warmbly-forms.service

feat: hosted lead-capture forms end to end: drag-and-drop builder with field settings, design panel, embed/share and submissions tabs in the dashboard, a public TanStack form app (forms/) served by the new standalone forms service (cmd/forms + internal/formserver) on FORMS_DOMAIN with per-form frame-ancestors CSP, honeypot/fill-time/Turnstile/per-IP submit protection and a same-origin JSON API proxying the backend internal API, form submissions creating contacts with categories and campaign enrollment plus realtime, audit, webhook and org-transfer coverage, migration 000114, seed forms, CI jobs, Dockerfile, systemd/nginx/compose manifests and docs

2026-09-01 01:17:51 -07:00

warmbly-install-release.sh

feat: address review on self-hosted updates: the updater no longer re-locks its mutex when a job finishes (every job used to deadlock at completion and freeze the status API), the backend caches the updater view so the member version pill, the health checks and the admin poll share one read and an absent updater is reported as not running rather than broken, the bare-metal upgrade builds unprivileged and hands off to a root-owned fixed-path installer that refuses symlinks so sudoers allows one command instead of install/cp/rm/chown/chmod/systemctl/ln, the installer fails when the backend does not come back, the seed image gets the version build args, the dashboard gates the update action on manage_settings and stops polling a backend that answers 404, and revived timestamps are typed as Date

2026-09-03 05:04:30 -07:00

warmbly-realtime.service

feat: add deploy/systemd units for backend, consumer, worker, tracking and realtime so a Docker-free install runs every service as the unprivileged warmbly user from /opt/warmbly with EnvironmentFile config

2026-08-29 23:37:22 -07:00

warmbly-tracking.service

feat: add deploy/systemd units for backend, consumer, worker, tracking and realtime so a Docker-free install runs every service as the unprivileged warmbly user from /opt/warmbly with EnvironmentFile config

2026-08-29 23:37:22 -07:00

warmbly-updater.service

feat: address review on self-hosted updates: the updater no longer re-locks its mutex when a job finishes (every job used to deadlock at completion and freeze the status API), the backend caches the updater view so the member version pill, the health checks and the admin poll share one read and an absent updater is reported as not running rather than broken, the bare-metal upgrade builds unprivileged and hands off to a root-owned fixed-path installer that refuses symlinks so sudoers allows one command instead of install/cp/rm/chown/chmod/systemctl/ln, the installer fails when the backend does not come back, the seed image gets the version build args, the dashboard gates the update action on manage_settings and stops polling a backend that answers 404, and revived timestamps are typed as Date

2026-09-03 05:04:30 -07:00

warmbly-worker.service

feat: add deploy/systemd units for backend, consumer, worker, tracking and realtime so a Docker-free install runs every service as the unprivileged warmbly user from /opt/warmbly with EnvironmentFile config

2026-08-29 23:37:22 -07:00

README.md

systemd units for a Docker-free install

One unit per Warmbly process, for a host where the binaries were built from source and installed under /opt/warmbly. The step-by-step guide that uses them is Deploying without Docker.

Unit	Runs	Reads
`warmbly-backend.service`	`/opt/warmbly/bin/backend`	`/etc/warmbly/warmbly.env`
`warmbly-forms.service`	`/opt/warmbly/bin/forms`	`/etc/warmbly/warmbly.env`
`warmbly-consumer.service`	`/opt/warmbly/bin/consumer`	`/etc/warmbly/warmbly.env`
`warmbly-tracking.service`	`/opt/warmbly/bin/tracking`	`/etc/warmbly/warmbly.env`
`warmbly-realtime.service`	`/opt/warmbly/realtime/bin/realtime start`	`/etc/warmbly/warmbly.env`
`warmbly-worker.service`	`/opt/warmbly/bin/worker`	`/etc/warmbly/worker.env`
`warmbly-updater.service`	`/opt/warmbly/bin/updater`	`/etc/warmbly/updater.env`

Every unit runs as the unprivileged warmbly user, may write only under /var/lib/warmbly (blob storage), and restarts on failure. Copy them to /etc/systemd/system/, then systemctl daemon-reload and systemctl enable --now the ones this host runs. Paths are plain strings, so sed them if you install somewhere other than /opt/warmbly.

deploy/config/env.example is the template for warmbly.env; the worker env file is what POST /api/v1/workers/enroll returns for an enrollment token.

warmbly-updater.service is the exception to the unprivileged rule: it runs as the user who owns the checkout (deploy in the unit; change it) and drives scripts/upgrade-bare-metal.sh, which builds unprivileged and then runs warmbly-install-release.sh (installed root-owned at /usr/local/sbin/warmbly-install-release) through sudo. That installer takes no arguments, touches only fixed paths and refuses symlinks, and is the single command to allow in sudoers. updater.env holds only UPDATER_TOKEN (the backend's INTERNAL_API_TOKEN). See Updates.