How 1mhdjant23/doc-incep works
Project type and purpose
• This is a containerized web‐infrastructure project built with Docker.
• It uses Docker Compose to assemble a three-tier WordPress application:
• A reverse-proxy web server (Nginx) with TLS termination
• A PHP-FPM/WordPress application server
• A MariaDB database with persistent storage
• The goal is to learn service isolation, inter‐container networking, and data persistence.
File structure
• Top-level:
• Makefile / README.md
• srcs/docker-compose.yml (central orchestration)
• srcs/requirements:
• mariadb/ (Dockerfile, custom my.cnf, setup script)
• nginx/ (Dockerfile, nginx.conf, .dockerignore)
• wordpress/ (Dockerfile, setup-wp.sh)
• Each service folder contains:
• Base image definition (Dockerfile)
• Configuration files and initialization scripts
• No separate frontend/backend folders: all services sit as containers, tied together by docker-compose.
README for additional insights
• Docker Compose defines networks and volumes.
• Nginx performs HTTPS termination, forwards PHP traffic to the WordPress container.
• WordPress (PHP-FPM) reads/writes to MariaDB via the internal Docker network.
• MariaDB data is persisted on a named Docker volume.
Detail
• Docker Compose file as a “control plane” element or annotation.
• Call out configuration files (nginx.conf, my.cnf) as mounted volumes.
• Initialization scripts (setup-wp.sh, set-up-db.sh) as part of the build step.
• Dependency order:
• First build images, then start mariadb, then wordpress, then nginx.