docker

Run the automated setup script (npm run docker:setup), which validates Docker, generates secrets, starts all containers, runs health checks, and executes Prisma migrations. Alternatively, start services manually with docker compose using the dev compose file and a project name flag.

Use the test compose file, which starts PostgreSQL on port 5433 and Redis on port 6380 so it runs concurrently with development. The automated test script handles startup, schema reset, test execution, and cleanup via trap handlers.

Another process is bound to the same host port. Identify it with lsof -i on the conflicting port, kill the process, switch to the test environment's alternate ports, or change the port mapping in the compose file.

Create a backup with docker exec pg_dump piped to a timestamped SQL file, optionally compressed with gzip. Restore by piping the SQL file into docker exec psql; production stacks also run automated daily backups at 2 AM.

In development, volume mounts provide hot-reload so code changes need no action. If dependencies changed, rebuild with docker compose up -d --build; for persistent caching issues, build with --no-cache or prune the system.

Check usage with docker system df, then clean up with docker system prune, volume prune, or image prune. For recurring issues, increase the disk image size in Docker Desktop resource settings.