chore: Dockerize dev and test environments

Author: flyingrobots

Dockerfile

@@ -0,0 +1,35 @@
+# syntax=docker/dockerfile:1
+
+# Base stage
+FROM node:20-slim AS base
+ENV NODE_ENV=production
+# Install Git (Required for git-cms)
+RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*
+WORKDIR /app
+
+# Deps stage
+FROM base AS deps
+COPY package.json package-lock.json* ./
+RUN npm ci --include=dev
+
+# Development stage
+FROM base AS dev
+ENV NODE_ENV=development
+COPY --from=deps /app/node_modules ./node_modules
+COPY . .
+# Configure Git for Dev
+RUN git config --global user.email "dev@git-cms.local"
+RUN git config --global user.name "Git CMS Dev"
+RUN git config --global init.defaultBranch main
+CMD ["npm", "run", "serve"]
+
+# Test stage
+FROM base AS test
+ENV NODE_ENV=test
+COPY --from=deps /app/node_modules ./node_modules
+COPY . .
+# Configure Git for Test
+RUN git config --global user.email "bot@git-cms.local"
+RUN git config --global user.name "Git CMS Bot"
+RUN git config --global init.defaultBranch main
+CMD ["npm", "run", "test:local"]

Dockerfile.test

@@ -6,13 +6,44 @@ A serverless, database-free CMS built on Git plumbing.
 
 **git-cms** treats your Git repository as a distributed, cryptographically verifiable database. Instead of files, it stores content as commit messages on "empty trees," creating a linear, append-only ledger for articles, comments, or any other structured data.
 
+## ⚠️ SAFETY WARNING
+
+**If you clone this repo and want to run the tests, ALWAYS run them in Docker.**
+
+The tests create, destroy, and manipulate Git repositories. While we try to use temporary directories, running low-level plumbing commands against your host filesystem is a risk you shouldn't take.
+
+We provided a safe harness:
+```bash
+npm test
+# (This automatically runs ./test/run-docker.sh)
+```
+
 ## Features
 
 - **Database-Free:** No SQL, No NoSQL. Just Git objects (Merkle DAG).
 - **Fast-Forward Only:** Enforces strict linear history for provenance.
 - **Atomic Publishes:** "Publishing" is just a pointer update (CAS).
 - **Infinite History:** Every draft save is a commit. Scrub back to any point in time.
 
+## Development
+
+We use Docker Compose to ensure a consistent, safe environment.
+
+### Start the Server (Dev Mode)
+```bash
+npm run dev
+# OR
+docker compose up app
+```
+The API and Admin UI will be available at `http://localhost:4637`.
+
+### Run Tests
+```bash
+npm test
+# OR
+docker compose run --rm test
+```
+
 ## Installation
 
 ```bash

README.md

@@ -0,0 +1,25 @@
+services:
+  app:
+    build:
+      context: .
+      target: dev
+    volumes:
+      - .:/app
+      - /app/node_modules
+    ports:
+      - "4637:4637"
+    environment:
+      - PORT=4637
+      - GIT_CMS_ENV=dev
+    command: npm run serve
+
+  test:
+    build:
+      context: .
+      target: test
+    volumes:
+      - .:/app
+      - /app/node_modules
+    environment:
+      - CI=true
+    command: npm run test:local

docker-compose.yml

@@ -8,6 +8,7 @@
   },
   "scripts": {
     "serve": "node bin/git-cms.js serve",
+    "dev": "docker compose up app",
     "test": "./test/run-docker.sh",
     "test:local": "vitest run",
     "test:e2e": "playwright test"

package.json

@@ -1,8 +1,5 @@
 #!/usr/bin/env bash
 set -e
 
-# Build
-docker build -f Dockerfile.test -t git-cms-test .
-
-# Run
-docker run --rm git-cms-test
+echo "🐳 Running tests in Docker..."
+docker compose run --rm test