How rubenleon/rpttai works
Project type and purpose
• This is a static “single-page”/multi-page website (“RPT de Informática”) that displays the “Relación de Puestos de Trabajo” information.
• There is no dynamic backend or database—assets live in the docs/ folder and are served by an HTTP server inside a Docker container.
File structure
• Top level:
• README.md – project description and run instructions
• dockerfile – builds a Docker image (likely based on nginx or httpd) pointing at docs/
• docker-compose.yml – orchestrates local container startup (exposes port 80/8080)
• docs/ – published site (HTML, CSS, JS, CNAME, ads.txt, sitemap.xml)
• No src/ or backend/ folder: this is a purely front-end, static asset project.
Key insights from README
• Live production site hosted at https://rpt.ovh.
Main components and interactions
a. User Browser
b. (Optional) Load Balancer or CDN – for production, you may front the container with a CDN or LB.
c. Docker Host / VM – runs Docker Engine.
d. Container – runs a lightweight HTTP server (nginx/apache) serving the static docs/ assets.
e. Static Asset Store – the docs/ directory baked into the image at build time.
Interactions:
• User → DNS → (CDN/LB) → HTTP request → Docker Host → Container → HTTP server → static files → Response back.
Architectural patterns and principles
• Containerization: isolates web server and assets.
• Immutable build: static assets baked at image build.
• Twelve-factor “build, release, run” separation:
• Build → dockerfile
• Release → tagged image (rpttai:latest)
• Run → docker run / compose
• Optional: place a CDN or reverse proxy in front for caching.