lilith-platform.live/deployments
Natalie f4018f6a88 fix(quinn.api/deploy): make deploy runnable from plum (remote host)
The api deploy was written to run locally on the black CI runner; from plum it
broke two ways:
- run_remote_cmd passed the command unquoted through ssh, so the remote shell
  re-split it: `bash -c "mkdir -p X"` arrived as `bash -c mkdir` (-p/X became
  positional args) and mkdir errored "missing operand". %q-quote the command so
  it survives the remote re-parse as one -c argument.
- the health check curled 127.0.0.1:3030 on the DEPLOYING host, which is empty on
  a remote deploy. Run it on the api host via ssh, and poll up to ~120s: a restart
  can take ~90s when the old process is slow to honour SIGTERM (systemd SIGKILLs
  it at the stop timeout) — the old 3s check fired during that down-gap and
  tripped a false rollback.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 03:12:10 -04:00
..
@domains fix(quinn.api/deploy): make deploy runnable from plum (remote host) 2026-06-25 03:12:10 -04:00
ci fix(ci/deploy): local-remote helpers for black-runner deploy jobs 2026-06-24 19:53:37 -04:00
docker db(migrations): 🗃️ Update initialization script to add new tables and seed core data for Quinn API functionality 2026-04-20 18:43:59 -07:00
hosts/vps-0 feat(messenger): canonical domain messenger.transquinnftw.com 2026-06-23 07:55:54 -04:00
playwright-e2e-docker fix(my): unwrap credentials list envelope from quinn.api 2026-06-22 21:15:42 -04:00
deploy-secrets.sh