Docs › Running MCDock

Database and standby server

SQLite by default, PostgreSQL with a standby for production.

Choosing

  • SQLite: one server, up to a few hundred users. Nothing to install.
  • PostgreSQL: production, a standby MCDock server, replicas and point-in-time recovery run by IT.

Moving

IT admin → Database. Every move takes a server backup, copies all records, reads them back and compares, then switches. The old copy is kept. If any step fails, nothing changes, and Git keeps working during the move.

Setting up PostgreSQL

On the database server (PostgreSQL 14 or later):

CREATE ROLE mcdock LOGIN PASSWORD '<strong password from the vault>';
CREATE DATABASE mcdock OWNER mcdock ENCODING 'UTF8';
  • Allow the MCDock servers in pg_hba.conf with scram-sha-256 and turn on TLS.
  • Connection string (no password in it): host=db1.company.local port=5432 dbname=mcdock user=mcdock sslmode=verify-full
  • The password goes in the password field and is stored sealed.

When the database stops answering

Pages show a red banner. Reading, clone and pull keep working, saving pauses, and MCDock reconnects by itself. Use Database → Diagnose, then Fix the connection if the password changed.

Updated 20 Nov 2026 · Something missing? Ask in the community.