How abdeladim-fadlane/42cursus-inception works
Main Components
• Docker Host / Virtual Machine: As the foundation where all Docker containers run.
• Docker Compose: Managed via the srcs/docker-compose.yml file, orchestrating all the services.
• Service Containers:
• Nginx Container(s): There are multiple Nginx services. One is under srcs/requirements/nginx (which contains its specific Dockerfile and conf), and Nginx is also involved in serving the bonus static website.
• MariaDB Container: Located in srcs/requirements/mariadb with its configuration files, Dockerfile, and auxiliary scripts.
• Wordpress Container: Under srcs/requirements/wordpress, with its configuration, Dockerfile, and setup script.
• Bonus Static Website Container: Found in srcs/requirements/bonus/static website, including its Dockerfile, index.html, and nginx.conf dedicated to serving static content.
• Additional Tools/Scripts: Found in the tools directory and within various script files inside the requirements folders, which support system administration and container setup.
Relationships and Interactions
• The Docker Compose file ties all these containers together, implying that container intercommunication (via networks) is essential.
• The Nginx components are likely the frontline (reverse proxy or load balancer) that directs external traffic to the respective application containers (Wordpress or static website) and might also handle static file serving.
• The Wordpress container communicates with the MariaDB container to perform database operations.
Architectural Patterns and Design Principles
• Containerized Microservices: Each service runs in its own container, isolating its environment and dependencies.
• Orchestration via Docker Compose: Indicates a modular design where dependencies and service lifecycles are managed centrally.
• Standardized Configuration: With dedicated directories for each service (e.g., configuration for Nginx, MariaDB) and accompanying setup scripts, the project emphasizes maintainability and ease of deployment.
• Separation of Concerns: By isolating each service (web server, database, CMS, static content), the design follows best practices for scalability and simplicity.
Relevant Technologies and Frameworks
• Docker and Docker Compose: Core technologies for containerization and orchestration.
• Nginx: Likely used both as a web server and reverse proxy.
• MariaDB: The database service for persisting data.
• Wordpress: The CMS running as an application service.
• Linux-based shell scripts: Used for configuration and automation.