Technical docs
Install and operate the Acorn CCMS stack.
Use these docs to run the Community Edition locally, evaluate a production deployment, and understand the services Acorn expects.
Local development
Quickstart
The local stack uses Docker Compose for infrastructure and a Next.js development server for the web app.
git clone https://github.com/Paint-The-Night/Acorn-CCMS.git
cd Acorn-CCMS
docker compose up -d
npm install
cd web
npm install
npm run db:generate
npm run db:seed
npm run dev
Deployment shape
Self-hosting architecture
Configuration
Environment files
Use committed examples as templates. Never commit real provider keys, database URLs, deployment dumps, or production `.env` files.
Local
Copy `web/.env.example` to `web/.env.local` and use Docker Compose defaults for local development.
Production
Use your host's secret manager. Rotate local defaults and require a strong `AUTH_SESSION_SECRET`.
Before real data
Production checklist
Reliability
Backup and restore
A useful backup strategy covers both PostgreSQL and object storage. A backup that has not been restored is not yet proven.
PostgreSQL
Schedule database dumps or managed snapshots. Keep restore instructions with the deployment runbook.
pg_dumpObject storage
Version or replicate document storage where possible. Confirm restore preserves private access controls.
S3Secrets
Backups are useless if production secrets are lost. Store secrets in a managed secret store.
SecretsMaintenance
Upgrades
Treat upgrades as application changes: read migrations, back up first, run smoke tests, and have a rollback path.
git pull
cd web
npm install
npm run db:generate
npm run db:migrate
npm run build