How logbyjungle/reverendtranslated works
Project type and purpose
• This is a full-stack, containerized web application (“ReverendTranslated”) built with Python/Flask.
• It scrapes chapters of *Reverend Insanity* from external sites, translates them via Google Translate through Selenium, then serves the results over HTTP/HTTPS.
• It uses Nginx as a reverse proxy in front of the Flask app, all orchestrated via Docker Compose.
File structure
• Top-level:
• Dockerfile, docker-compose.yml, entrypoint scripts – define and run containers
• nginx.Dockerfile, nginx.conf/https, entrypoint_nginx.sh – build and configure the Nginx proxy
• main.py & bot.py – Flask application and translation logic
• static/ & templates/ – front-end assets (CSS, JS) and Jinja2 HTML views
• requirements.txt, languages.txt – dependencies and supported languages list
• There is no dedicated database; the app fetches, translates, and serves content at request time.
• No separate microservices beyond the Nginx proxy and single Flask container.
Key insights from the README
• The app listens on port 5000 by default; Nginx fronts it on ports 80/443.
• Deployment instructions involve replacing domain names in nginx.conf, using DuckDNS for dynamic DNS, and managing certificates with certbot.
• TODOs highlight security, parallel requests, and CI as future improvements.
Emphasizing essential architectural details
• That Nginx handles SSL termination and forwards only to the Flask container.
• That translation is synchronous within the request path (for now), and mark this as a performance hotspot for future refactoring.
• Docker Compose orchestration layer by grouping the Nginx and Flask containers inside a single “Docker Network” boundary.