How 7dg84/cecyayuda works
Project type and purpose
• This is a containerized, full-stack web application (“CECyAYUDA”) that serves user-facing HTML/JS/CSS pages and PHP-based endpoints, backed by a relational database.
• Key indicators:
• Top‐level folders: “db” (database scripts), “nginx” (reverse proxy), “webpage” (web app).
• A docker-compose.yml that wires up three containers (db, nginx, webpage).
• Static assets, PHP scripts, Composer dependencies under “webpage”.
File structure
• db/
• Dockerfile and a SQL dump (cecyayuda.sql) to build a MySQL (or MariaDB) image.
• nginx/
• Dockerfile and default.conf define an Nginx container to serve static files and reverse-proxy PHP requests.
• webpage/
• Dockerfile builds a PHP runtime with your application code, Composer dependencies, and static assets.
• Colonias/ HTML pages (static).
• PHP endpoints (consultar.php, save-report.php, admin/*.php, logic.php, etc.).
• JS under scripts/, CSS under styles/.
• docker-compose.yml
• Orchestrates three services: db, nginx, webpage.
• loadhtdochs.py
• A utility script (likely data loader or maintenance tool) run from the host or in a separate container.
README for additional insights
• Minimal instructions: “docker compose build” and “docker compose up -d.”
Detail without overthinking
• Static Assets (Colonias/*.html, styles/, scripts/)
• PHP API Layer (logic.php, save-report.php, admin/*.php)