How alepeteporico/proyecto_integrado works
Project Type and Purpose
• This is a full-stack, multi-service application orchestrated with Docker Compose.
• It bundles three major web applications—Redmine, Moodle, and WordPress—behind a centralized OAuth2-proxy for authentication, and persists data in Docker-mounted database volumes (PostgreSQL for some services and MySQL for Redmine).
File-Structure Analysis
• Top‐level “docker” directory holds certificates, a PostgreSQL data volume (docker/db), and a docker-compose.yml that ties all containers together.
• Folders moodle, redmine, wordpress-docker-compose contain the application artifacts (tarballs, plugin code) and/or secondary Compose files.
• The presence of oauth2-proxy-v6.1.1.linux-amd64 indicates an OAuth2 authentication gateway.
• Under redmine/db there’s a full MySQL data directory (InnoDB files, schema, etc.), so Redmine uses MySQL.
Essential Details to Capture
• The chain of authentication and routing via OAuth2-Proxy
• Per-service persistence: PostgreSQL vs. MySQL
• Docker Compose as the central orchestration mechanism
• TLS termination using docker/certs
• Volume mounting strategy for database durability