MemoPop Connector API, Phase 2: Deploy
A container with every system tool the memo needs, running on Railway at memopop.didi.sh, watched by a health check every 30 minutes.
- Path
- plans/MemoPop-Connector-API-Phase-2-Deploy.md
- Authors
- Michael Staton
- Augmented with
- Claude Code on Claude Opus 5.5 (1M context)
- Tags
- Plan · MemoPop · Railway · Deployment · Monitoring
MemoPop Connector API, Phase 2: Deploy
Numbered 2 in the spec, run after 4, 5, and 6 so the first deploy carries the whole API. Read the spec (§Storage, §Auth, §The test suite, layer 10) and [[Host-the-Connector-on-Railway-at-memopop-didi-sh]].
Split of work
The engineer builds and tests everything that runs locally. The VP Eng
does everything outward-facing, with the operator’s yes: creating the Railway
service, volume, and bucket, setting variables, DNS for memopop.didi.sh, and
the first deploy.
Engineer steps
- Failing test for
CONN-LIVE-01: the health-check script run against a local server (uvicorn in a fixture) passes; with a step forced to fail or to be slow, it exits non-zero naming the step. scripts/health_check.py: given a base URL and a key, create a uniquely named deal intest-firm, add a small inline material, take one research step and one draft step with canned artifacts, compile, then mark the deal archived. Time each call against its documented worst case.Dockerfile: Python 3.11 slim;uvinstall; pandoc, WeasyPrint’s libraries, poppler, tesseract, ghostscript, ImageMagick, and thejjbinary. Runsuvicornon$PORT, honouringX-Forwarded-*from Railway’s proxy.MEMO_IO_ROOT=/data/firms. Build it locally and run the health check against the container..github/workflows/live-health.yml: every 30 minutes and on manual dispatch, runs the script againsthttps://memopop.didi.shwith the key from repository secrets.CONN-LIVE-02is a gated test that runs only whenMEMOPOP_LIVE_URLis set.docs/operator/deploy.md: the variables, the volume, the bucket per firm, provisioning a firm, disabling a step.- Changelog, commit, push. Report what the VP Eng needs to provision.
VP Eng steps (operator approval first)
Railway project and service from the repo’s development branch, a volume
at /data, a bucket for test-firm, the variables, a custom domain
memopop.didi.sh (DNS record where didi.sh’s DNS lives), the first deploy,
then CONN-LIVE-02 and one manual health-check run.