How nfqakademija/podcast works
Project type and purpose
• This is a full-stack web application built with Symfony (PHP) that aggregates Lithuanian basketball podcasts from multiple sources, enriches them using the YouTube API and a custom crawler, stores everything in MySQL, sends various newsletters, and exposes both a public-facing site (Twig + CSS/JS assets) and CLI commands for data collection.
File structure
• Top-level “src/” holds the Symfony application:
• Controllers (web endpoints)
• Services (CrawlerService, YoutubeService, MailService, etc.)
• Entities + Repositories (Podcast, Source, Subscriber, User, Comment, Tag)
• Commands (NewsletterSendingCommand, PodcastsCollectingCommand)
• EventListener (SendConfirmationEmailListener)
• “templates/” houses Twig templates for UI and emails
• “assets/” + webpack.config.js for frontend CSS/JS, built via Webpack Encore
• “public/” is the document root (index.php, static assets)
• “config/” holds all Symfony and environment configuration
• “scripts/” and “.deploy/” scripts for Docker orchestration, building, deployment
• Docker-related files (Docker Compose YMLs, .env, .env.test) indicate a containerized setup
README for additional insights
• Uses PHP 7.3, MySQL, Nginx, Docker
• Core features: filters, search, RSS, likes/dislikes, listen later, comments, multiple newsletter flows
• Integrations: Symfony DomCrawler for scraping, YouTube Data API v3, Mailer URL (SMTP or API)
• CLI commands for initial data collection and recurring podcast collection
Elements
• Browser ↔ Nginx → Symfony HTTP
• Symfony HTTP → Doctrine → MySQL
• Cron/CLI → Symfony Console → Services → MySQL
• Symfony Services → External APIs (YouTube, Mailer)
• Green for external services
• Blue for containers/services you manage
• Orange for data stores
• Protocols where relevant (HTTP, TCP/MySQL, SMTP/Web API)