Docker IPTV Backend System – Multi-User, Single URL, Proxy-Ready Description: I need a developer to build a Docker-based IPTV backend system using Threadfin or similar. This is Phase 1, but it must be designed so a future proxy/gateway layer can be added later without rebuilding the system. Main goal I want one central system where I can manage IPTV users, playlists, and EPGs easily. Users should connect using one fixed public URL, while the backend handles the individual user setup. Requirements - One master config for channels, playlists, and EPG - Separate isolated user instance/config per customer - CLI/script to create, list, remove, and recreate users - Automatic port assignment with no conflicts - One public-facing URL/domain for all users - Internal routing to the correct user instance - No exposed per-user ports to customers Playlist / EPG - Generate one M3U per user - Generate one XMLTV EPG per user - M3U must include "url-tvg" - Support multiple XMLTV sources - Merge/map EPG sources into one final output - Clean channel groups and remove duplicates Central control - Update master config once and sync to all users - Provider/base URL must be stored centrally, not hardcoded - Ability to change upstream/provider URL once and regenerate all users - User credentials must remain separate Proxy-ready architecture Phase 1 must be built so a future Phase 2 proxy/gateway layer can be inserted later. This means: - upstream/provider access must be abstracted via config/env/templates - no direct hardcoded provider URLs inside user configs - backend routing should allow provider traffic to be redirected later through a gateway/proxy layer - user-facing URL should not need to change when Phase 2 is added Deliverables - Docker Compose setup - config templates - user management scripts - reverse proxy setup for single public URL - backup/restore process - simple documentation - working demo with at least 2 users Timeline Around 7 days for working Phase 1. Important This phase is not for ISP blocking or proxy/VPN work yet. But the system must be built so that can be added later cleanly. Please reply with your approach and relevant Docker/IPTV automation experience.