Deployment
The four-service production shape every route deploys, and the chooser: Coolify guided, Compose by hand, or Vercel without a server.
A production Meith board is four services, whichever route puts them there:
- PostgreSQL stores everything the community makes.
- A one-shot migration service updates the schema, and finishes before anything else starts.
- The web service answers browsers and the API.
- The worker runs scheduled and queued work once a minute.
Every route below deploys that same shape from the same image, and ends
the same way: open /install on the new board to name it and create its
first administrator. Nothing is built on your server — the deploy pulls
an image that was built and tested when the release was cut.
Pick your route
| Route | For | You need |
|---|---|---|
| Coolify | Most boards — the guided route | A rented server and a domain; no terminal required after setup |
| Docker Compose by hand | Operators who already run a proxy | Docker Compose, a .env you write, a reverse proxy you operate |
| Vercel | Boards that would rather not have a server | A Vercel account and a hosted Postgres; the worker becomes a cron tick |
If you only want something the public can poke, demo mode runs a board that resets itself on a schedule.
After it is up
- Operations — health checks, configuration, mail, backups, and the operator CLI.
- Upgrading — moving between released versions safely; the board, its plugins and the compose file carry one version number and move together.
- Monitoring — what to alert on once people rely on it.