Loading...
Loading...
Operate a self-hosted Customermates deployment with Docker Compose updates, restarts, logs, resets, and troubleshooting workflows.
This page covers the ongoing maintenance of a self-hosted Customermates deployment. If you have not installed the stack yet, start with Self-Hosting Get Started.
Self-hosted mode runs the community edition. Paid Enterprise features (Audit Logging, Single Sign-On, AI Agent, Whitelabeling) are unavailable unless explicitly licensed and enabled in your deployment model.
From your deployment root:
chmod +x scripts/selfhost-update.sh
./scripts/selfhost-update.shOptional: pull latest git changes before rebuilding:
./scripts/selfhost-update.sh --pullThe update script:
prisma migrate deploy.After every update, verify service health with docker compose ps.
Use the restart helper when configuration changes require a clean restart:
chmod +x scripts/selfhost-restart.sh
./scripts/selfhost-restart.shThis script should restart the stack safely and print health and log pointers. It does not run migrations.
Most operational issues can be diagnosed with container logs:
docker compose logs -f app
docker compose logs -f postgresUseful checks:
docker compose ps to inspect service state and healthdocker compose config to validate merged Compose configurationdocker compose exec app sh to inspect runtime environment inside the app containerDaily operations you may use:
docker compose up -d
docker compose down
docker compose pull
docker compose build --no-cache app
docker compose restart appUse targeted restarts (docker compose restart app) when only the application changed.
Use the reset helper only when you intentionally want to wipe local deployment data:
chmod +x scripts/selfhost-reset.sh
./scripts/selfhost-reset.shThe script requires explicit confirmation (RESET) before deleting volumes.
For production deployments, maintain a backup and restore routine:
If you are just getting started, go back to the Self-Hosting quick setup.