Bot Subte v3 - Arquitectura Modular

Changes and Improvements

1 - Complete Refactoring: The bot evolved from a single monolithic script into a modular, service-oriented architecture. The codebase is now clean, well-organized, and follows the single responsibility principle.
2- Fixed Data Persistence: Docker Compose volume mapping was corrected. The alert history file (src/data/estados_persistentes.json) is now properly stored on the host, surviving container restarts.
3 - Configuration Isolation: Centralized environment variable management (Token, Chat ID, schedules) was implemented through config.py.
4 - Technical Confirmation of Data Extraction: After an in-depth network audit (reverse engineering), the need for headless Selenium was confirmed to handle dynamic data injection (SignalR) from the EMOVA website. The scraping engine is now robust and reliable.
5 - Optimized Infrastructure: RAM limits and shared memory (shm_size) were fine-tuned in the container to ensure Chromium stability in cloud environments (GCP).
6 - Professional Documentation: The README.md files (Spanish and English) were completely rewritten, including diagrams of the new project structure.

Bot de Alertas de Tránsito Buenos Aires v2.0

Release v2.0 - Monetti Agustin

• Updated the bot's message structure: This change provides better readability. Key information like line names is now bold and underlined to stand out.
• Correct: .env support: All secrets and config keys (like the Bot Token) are now loaded from an environment file. This is more secure and makes setup much easier.
• Cleaner architecture: Refactored the code to better separate concerns (fetching data vs. formatting messages vs. sending alerts). This makes the project easier to maintain and build upon.

Bot Alerta Funcionamiento Subte Argentina

Bot automatizado que monitorea el estado de las líneas del subte de Buenos Aires y envía alertas a Telegram cuando detecta cambios en el servicio.

• Utiliza Selenium para navegar y extraer el estado de cada línea desde la web oficial de EMOVA.
• Si detecta que alguna línea no está en estado "Normal", envía una alerta automática a un chat de Telegram configurado.
• El chequeo se realiza de manera periódica (por defecto, cada 1.5 horas).