Skip to content

Docker Deployment

How to run Postgram from the pre-built image and when to switch from local build mode.

  1. Pull the image:
Terminal window
docker pull ghcr.io/ivo-toby/postgram:latest
  1. Use the latest tag for the mainline build, or sha-<short> for pinning.

  2. In docker-compose.yml, swap the mcp-server service from local build to image mode:

services:
mcp-server:
image: ghcr.io/ivo-toby/postgram:latest
# remove build: .
  1. To support native remote connectors, expose Postgram over public HTTPS and set:
Terminal window
OAUTH_ENABLED=true
PUBLIC_BASE_URL=https://<your-postgram-host>

The connector URL is ${PUBLIC_BASE_URL}/mcp.

  1. Start the stack:
Terminal window
docker compose up -d
  • The repository default Compose file builds locally by default; image mode is useful for quick deployment and upgrades.
  • ghcr.io/ivo-toby/postgram:main maps to the same mainline build as latest. Pin sha-<short> when an immutable image reference matters; pushed v* tags also publish semantic image tags.
  • If clients upload synced markdown through a reverse proxy, configure request body limits above the sync batch size. The bundled UI nginx proxy sets client_max_body_size 64m.
  • See the OAuth connector guide for the full remote MCP setup.