Operate and update Prism

A few good habits to keep Prism running over time.

Back up before making changes

Keep your configuration, PostgreSQL data, workspace and server volumes, and any folders mounted from the host. Copying the repository alone does not back up Docker volumes.

Plan a consistent database backup, protect configuration secrets and test restoration on a separate installation. Exact paths and volumes depend on your deployment.

Update Prism

Review repository changes, back up, then choose your update method. To use published images with Compose:

git pull --ff-only
docker compose pull
docker compose up -d

If you build from source, rebuild the relevant services. Running git pull alone does not update the images currently running.

Access Prism remotely

Keep authentication enabled and configure HTTPS with a reverse proxy for your domain. Embedded service routing under *.localhost is designed for local access: reaching those services remotely requires additional network configuration.

The default Docker mode uses the host daemon. Docker socket access provides extensive control over the machine, so reserve this deployment for trusted users. Workspace mode has separate prerequisites.

Inspect and troubleshoot

docker compose ps
docker compose logs --tail=100 prism-server

Before sharing logs in an issue, remove keys, private addresses and personal data. Include the version, reproduction steps and expected result.