How ismaelph/despliegue-app-web works
Overall Project Context
• The project is titled “Despliegue de Aplicaciones Web” and is designed as a series of deployment exercises. It covers multiple technology stacks and methods (Docker, Vagrant, Git, etc.).
• Each UT (UT1, UT2, UT3, UT4, UT5) represents a different deployment scenario:
• UT1: Uses both Docker Compose and Vagrant environments.
• UT2: Focuses on deployment via different docker-compose setups, one of which integrates with DuckDNS and another with a general configuration that includes a Caddyfile (reverse proxy/webserver).
• UT3: Contains several examples for diverse frameworks—Flask (Python), JakartaEE (Java), Laravel (PHP), Node.js (JavaScript)—and demonstrates using Docker containers for each.
• UT4: Deals with a Git-based deployment practice (hook scripts, bare repositories) in addition to Dockerized components.
• UT5: Demonstrates network-oriented or infrastructure services like DNS (dnsmask) and LDAP.
File Structure and Architectural Patterns
• There are top-level directories (ut1-Compose, ut1-Docker, ut2, ut3, ut4, ut5) that clearly separate different deployment experiments.
• Each UT folder often contains a README and a “docker” or “docker-compose.yml” file. This indicates the heavy use of containerization.
• The presence of Vagrant files (Vagrantfile, provisioning scripts) in some UTs (UT1 and UT2) suggests virtual machines act as environments hosting one or several containers.
• Besides code-related folders, there is a “datos_varios” directory holding images and logs, which are used for documentation and display of technologies.
a. Your Main Components:
• Virtualization Layer: Illustrate VirtualBox running Vagrant-managed VMs.
• Container Layer: Represent Docker orchestration with containers and docker-compose configurations.
• Deployment & Integration Tools: Include the Git-based deployment components (UT4) and infrastructure integrations (DNMask and LDAP in UT5).
b. Relationships and Interactions:
• How Vagrant VMs (in UT1) host Docker containers using a docker-compose file.
• For UT4, indicate the Git repository (and hook scripts) flowing changes to deployed applications.
• For UT5, illustrate how the DNS mask or LDAP service connects with the overall network layer or provides infrastructure-level services.
c. Architectural Patterns:
• Containerization and orchestration are central: Docker, docker-compose, and Vagrant serve as key tools.
• Separation of concerns is visible with each UT being a self-contained experimental module, reflecting a micro- or modular architectural approach.
d. Incorporate Key Technologies:
• Docker and docker-compose as building blocks for containers.
• Vagrant and VirtualBox for VM-based isolation.
• Frameworks (Flask, JakartaEE, Laravel, Node.js) denoting the application layer.
• Reverse proxies (Caddy) to manage incoming traffic.
• Git hooks and bare repositories for deployment automation.
• DNS and LDAP for networking and directory services.
• Every component is clearly labeled with its role (for instance, “Vagrant VM with docker-compose” or “Caddy Reverse Proxy”).
• If relevant, include notes about configuration files (like Vagrantfile, docker-compose.yml) to indicate where orchestration or provisioning takes place.