Deploy and Host Mosaic on Railway

Mosaic is a WhatsApp chief-of-staff: type /sotu, /pending, /stats, /recap, /eli5 in any group and the answer is delivered privately to your own "Message yourself" chat — the group you typed in is never written to.

About Hosting Mosaic

One Docker container (Go WhatsApp bridge + Python command engine) and one Railway volume mounted at /data — attached automatically by this template — which holds your WhatsApp pairing and message history across redeploys. Keep the service at one replica.

Why Deploy Mosaic on Railway?

Volume, restarts, health checks and the public URL are configured for you.
Nothing else to install: pairing and settings happen from the browser once, then from WhatsApp (/help).
Owner-only commands; answers never post into groups.

Common Use Cases

Operators sitting in 30–100 WhatsApp groups who lose track of what people asked them.
A daily /pending open-loops ledger grouped by who owes what — in your Me chat.
Catching up on a noisy group with /recap without posting anything into it.

Dependencies for Mosaic Deployment

No external dependencies beyond your own accounts. At deploy time you will be asked for exactly two things:

variable	what to enter
`GEMINI_API_KEY`	a Gemini key from a billing-enabled project: https://aistudio.google.com/apikey
`SETUP_PASSWORD`	a password for the web pairing page (used once, to scan the QR)

Timezone defaults to Asia/Kolkata; add a TZ variable later if you need another.

After deploy: open the service URL, log in with SETUP_PASSWORD, scan the QR under WhatsApp → Linked devices, wait for Connected as +91… · Me chat: …, then type /pending in any group. Tips and troubleshooting: https://github.com/sameer-hoda/wa-slash-commands/blob/master/docs/RAILWAY.md