How frappe/frappe_docker works
Frappe Docker packages container images and Docker Compose configurations for deploying Frappe applications. The principal workflow is: an operator selects a demo or production configuration, Compose provisions application and infrastructure containers, site initialization configures the bench and database, and users reach the running Frappe site through the proxy. Documented branches include custom images, MariaDB/PostgreSQL, Redis, TLS, backups, multi-tenancy, and development environments. The graph reflects sampled installer behavior and README/tree capabilities; several Compose relationships are represented at configuration level.
Main entry points: installer.py Site Initializer · compose.traefik.yaml HTTP Proxy · pwd.yml Demo Compose · compose.yaml Production Compose
Components 19
Deployment Configuration
- Demo Compose
pwd.yml - Production Compose
compose.yaml - Compose Overrides
overrides
Container Images
- Custom Image
images/custom/Containerfile - Production Image
images/production/Containerfile
Frappe Runtime
- Runtime Entrypoint
resources/core/start.sh - Nginx Entrypoint
resources/core/nginx/nginx-entrypoint.sh - Site Initializer
development/installer.py - Application Database
overrides/compose.mariadb.yaml - PostgreSQL Database
overrides/compose.postgres.yaml - Redis Services
overrides/compose.redis.yaml - HTTP Proxy
overrides/compose.traefik.yaml
Operations
- TLS Integration
overrides/compose.https.yaml - Backup Scheduler
overrides/compose.backup-cron.yaml - Development Environment
development - Operations Guidance
docs
Other components
- Operator
- Site User
- Docker Engine
Connections 19
- Operator → Demo Compose: selects setup
- Operator → Production Compose: selects setup
- Operator → Compose Overrides: adds options
- Demo Compose → Docker Engine: starts services
- Production Compose → Docker Engine: starts services
- Compose Overrides → Docker Engine: modifies services
- Docker Engine → Production Image: runs image
- Docker Engine → Custom Image: runs image
- Production Image → Runtime Entrypoint: launches runtime
- Runtime Entrypoint → Nginx Entrypoint: starts web layer
- Site Initializer → Application Database: creates site
- Site Initializer → PostgreSQL Database: creates site
- Site Initializer → Redis Services: configures queues
- Nginx Entrypoint → HTTP Proxy: serves traffic
- Site User → HTTP Proxy: requests site
- TLS Integration → HTTP Proxy: secures traffic
- Backup Scheduler → Application Database: backs up data
- Development Environment → Site Initializer: supports setup
- Operator → Operations Guidance: follows guidance