How nithincninan/magento2-docker works
Project type and purpose
• This is a Docker-based development environment for running a Magento 2.4.x e-commerce application.
• It uses Docker Compose to wire up multiple containerized services (web server, PHP-FPM, database, caches, search engine, message queue, developer tools).
File structure
• Top-level Docker Compose definitions:
• docker-compose.yml (production)
• docker-compose.dev.yml (development)
• docker/nginx: Dockerfile + custom Nginx configs (default.conf, m2-config/nginx.conf)
• docker/php: Dockerfile + PHP-FPM pool config (www.conf)
• .env for environment variables, .github/workflows/docker-image.yml for CI, hosts Mageto code under magento247 folder.
Main components
a. Developer workstation
• Hosts code, runs Docker CLI, PHPStorm + Xdebug
b. Reverse proxy / web server
• Nginx container (port 80 → Magento frontend/admin)
c. Application
• PHP-FPM container running Magento code at /var/www/magento247
• Xdebug frontend in PHP container
• Blackfire Probe + CLI inside PHP container, Blackfire agent container
d. Persistent data stores
• MariaDB container (MySQL 10.6)
• Redis container (session & page-cache DBs 0–2)
• OpenSearch container (catalog search index)
• RabbitMQ container (message queue for asynchronous tasks)
e. Developer support tools
• MailHog container (SMTP catch-all & UI on port 8025)
• RedisInsight container (Redis GUI on port 8001)
• OpenSearch Dashboards container (Kibana-like UI on port 5601)
Relationships & data flows
• HTTP request → Nginx → proxy_pass to PHP-FPM
• PHP-FPM ↔ MariaDB for CRUD operations
• PHP-FPM ↔ Redis for session & cache reads/writes
• PHP-FPM ↔ OpenSearch for catalog search indexing & queries
• PHP-FPM → RabbitMQ for enqueuing background jobs → PHP-FPM workers consume
• PHP-FPM → MailHog SMTP port for transactional emails
• PHPStorm ↔ PHP-FPM (Xdebug) and PHPStorm ↔ Blackfire client → Blackfire agent → Blackfire cloud
Architectural patterns & design principles
• Container-per-service (microservices-style)
• Single Docker network (magento_network) connects all services
• Clear separation of concerns: web proxy, app runtime, data persistence, dev tools
• Environment configuration via .env, docker-compose overrides for dev/prod
Essential elements
• Exact container names (nginx, php, mariadb, redis, opensearch, rabbitmq, mailhog, redisinsight, opensearch-dashboards, blackfire)
• Volume mounts (./magento247 → /var/www/magento247)
• Port mappings (80, 9000, 3306, 6379, 9200, 5672, 8025, 8001, 5601)
• FastCGI connection between Nginx and PHP-FPM
• Network name (“magento_network”) encapsulating all services