// the find
frappe/frappe_docker
Docker environment for developing, deploying, and running Frappe applications (ERPNext and custom apps) in production and development
Official Docker setup for Frappe applications — ERPNext, CRM, Helpdesk, and custom apps built on the Frappe framework. Covers everything from a one-command demo to multi-tenant production deployments with Traefik or nginx. If you're self-hosting ERPNext, this is where you start.
The override compose file pattern is genuinely well-thought-out: a base compose.yaml plus purpose-specific overrides (traefik, postgres, backup-cron, custom-domain-ssl) that you compose together rather than forking a monolithic file. Documentation is unusually complete for an infra repo — numbered sections covering setup, operations, migration, troubleshooting, and ARM64 quirks. CI pipeline builds and publishes both stable and develop images automatically, so you're not stuck waiting on a maintainer to cut a release. The devcontainer setup with VS Code launch configs is a practical shortcut for custom app development.
Frappe itself is not a simple application — it brings MariaDB or Postgres, Redis (cache + queue + socketio), nginx, a background worker, and a scheduler, so the compose stack is genuinely heavy and the 'disposable demo' caveat in pwd.yml is a real footgun for people who skip the warning. No Kubernetes manifests in the repo; there's a separate frappe/helm-charts project, so you're on your own for anything beyond docker compose. The Postgres support is a compose override, not a first-class path — most docs and examples default to MariaDB, which can surprise people who want to run on Postgres from the start. Fork count (2593) is higher than stars (2434), which usually signals a lot of people are pinning private customizations rather than contributing upstream — the community fragmentation around custom app builds is a real maintenance headache.