• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: October 16th, 2023

help-circle









  • If you had monitoring, you wouldn’t have taken 6 hours to catch it.

    I’d say learn HA anyway because it’s a good skill, but that doesn’t prevent you from having the other parts I mentioned. I say this because, again, unless you are experienced with HA, there will be edge cases where it’s not going to do what you though it would do, and your service will be down all the same. Monitoring/alerting and one-click/shell script install will be much more valuable in the short-mid term.



  • HA involves many factors: service uptime, link uptime, db uptime, etc. I’d probably put a reverse proxy in front and use the servers as upstream. web servers tend to be more reliable, so in your case a single instance ought to suffice.

    Aside from actual HA tools, your most important asset in this stage is a uptime check service that pings your server every n seconds, a reliable backup/restore procedure, and a one-button deployment strategy.

    Shits can and will probably happen. What are you going to do when it does? And how fast can you respond? I say this because you most likely won’t get HA right in the first, second, or third time, unless you already have tons of experience behind you. Embrace failure and plan accordingly.


  • Your main dividing factor in this regard is if you want to do transcoding or not. If so, you need to pick a CPU with good iGPU, and for Intel that starts on the 8th gen. Older gens work well for 1080p, but for 4k they aren’t great. I have a i5-7500 that couldn’t do 4k HEVC without lag (although I was using it as HTPC. Maybe headless would be enough?)

    For anything else, mostly any computer will do. Most of the stuff you host will be idle most of the time, so your CPU only needs to be powerful enough for the apps you are using at the moment.