How internetee/docker-images works
Main Components
• Docker-Compose Orchestrator – Represent the docker-compose.yml that brings everything together.
• Nginx Container – Mark as a “reverse proxy” with its configuration files found in the nginx directory. Show that it routes incoming HTTPS requests (via domains like registry.test, auction.test, registrar.test, etc.) to appropriate backend services.
• Registry (handling EPP requests and portal interface)
• Rest WHOIS
• Auction Center
• (and implicitly WHOIS and possibly EPP Proxy as individual components)
That these containers are Ruby applications served by Puma. Link that these components are built on various Ruby base images, as shown in your “base_images” directory (listing Ruby 2.4, 2.5, ... up to Ruby 3.3.1).
• Postgres Container – With a dedicated persistent volume (data not removed on docker-compose down). Represent its connectivity with the application containers.
• Certificate Authority (CA) / Shared Persisted Certificate Store – Represent the “shared/ca” directory (mirrored into the containers as /opt/ca) where certificate generation and storage are managed. Indicate that this is used across containers to generate and trust self-signed certificates.
Relationships and Interactions
• Application containers communicate with the Postgres container for database operations. Show these interaction paths.
Architectural Patterns and Design Principles
• Separation of concerns – The reverse proxy (nginx) is distinct from the application servers.
• Modularity provided by docker-compose: each component (registry, auction_center, rest-whois, etc.) runs as an independent service, yet they work together.
• “build once, run anywhere” principle: Using various Dockerfiles and scripts under “base_images” to create tailored Ruby environments for each service.
• Clear indication of shared assets: The certificate authority and persistent Postgres volume ensure both security and data persistence across containers.
Points to Emphasize
• Iterative development process – for example, note that docker images are rebuilt when gemfiles change.
• Make explicit the container and host relationship: how /opt/ca is mounted from shared/ca, and how configuration files (like nginx’s and registry’s YAML files) are used.
• That the system handles security via certificate generation and that multiple services are served over HTTPS, with explicit instructions provided in the README.