Hetzner Live Streaming Server Setup
Budget: £20 – £250 GBP
I need a fresh account spun up on Hetzner (or an equivalent provider) and configured so Channel-U TV, my YouTube-style site at channel-u.tv, is fully operational again. The landing page currently explains the outage; once the new environment is ready the domain should point straight to it with zero downtime for viewers.
Key requirements are clear: plenty of storage for an expanding library, rock-solid performance for 24/7 live streams, and an architecture that plugs smoothly into the existing PHP/Laravel front-end and its video modules. A hybrid drive layout— SSD for active streaming segments and HDD for large video archives— suits the workload best, so please provision and mount it accordingly.
SSL must be installed and enforced across all sub-domains. If you prefer to fold that into an automated Let’s Encrypt routine, great; just document the renewal process for me.
Once the server is live I’ll need the video encoder/packager (FFmpeg, NGINX-RTMP or a comparable stack) tuned so streams start instantly, the player picks the right bitrate, and uploaded videos hit storage without manual intervention. When you hand over, I expect:
• channel-u.tv resolving to the new box over HTTPS
• live stream publishing and playback tested from OBS and the site player
• existing database and media migrated intact
• admin credentials plus a short step-by-step runbook for future scaling
If something in this outline can be improved— load balancers, optional DDoS layers, alternative CDN hooks— feel free to suggest it, but SSL, hybrid storage and high-performance streaming are non-negotiable.
Key requirements are clear: plenty of storage for an expanding library, rock-solid performance for 24/7 live streams, and an architecture that plugs smoothly into the existing PHP/Laravel front-end and its video modules. A hybrid drive layout— SSD for active streaming segments and HDD for large video archives— suits the workload best, so please provision and mount it accordingly.
SSL must be installed and enforced across all sub-domains. If you prefer to fold that into an automated Let’s Encrypt routine, great; just document the renewal process for me.
Once the server is live I’ll need the video encoder/packager (FFmpeg, NGINX-RTMP or a comparable stack) tuned so streams start instantly, the player picks the right bitrate, and uploaded videos hit storage without manual intervention. When you hand over, I expect:
• channel-u.tv resolving to the new box over HTTPS
• live stream publishing and playback tested from OBS and the site player
• existing database and media migrated intact
• admin credentials plus a short step-by-step runbook for future scaling
If something in this outline can be improved— load balancers, optional DDoS layers, alternative CDN hooks— feel free to suggest it, but SSL, hybrid storage and high-performance streaming are non-negotiable.