Linux is fun! Of course it’s doable. At first you’ll have a hard time and need to look up everything at ddg or whatever. But you’ll learn a lot. Go in small steps. One thing at a time. And envision the feeling you’ll get when you succeed!
I’d go for HLS due to its simplicity: just files over http(s). VPN or not - depends on your network. If your machine is accessible from the internet, just putting the files into a webserver subdirectory with a long random path and using https will be secure enough for the usecase. Can be done with an ffmpeg oneliner.
The downside of HLS is the lag (practically – 10s or more, maybe 5 if you squeeze it hard). It is in no way realtime. Webrtc does it better (and other things too), but it is also a bigger pain to set up and forward.
Also, just in case, test that the webcam works fine if left active 24/7. I had (a cheapo) one that required a powercycle after a week or so…
Networking will take you from being “they guy that fixes computers” to full blown Telco engineer. It’s a lot though, more than I can explain. Get managed switch and start having LAN parties.
The guide above doesnt include Audiobookshelf installation, but you will quickly see that adding Audiobookshelf to the basic setup is very easy. There are two things I’ve learned since the initial setup, which are worth a deviation from the guide above.
First, the recommendation in the guide to use a separate userid and groupid (1001) for the docker containers vs. your own userid/groupid (1000) is a royal PITA and not necessary for most basic use cases.
Second, and much more important, you MUST set up your VPN in a Gluetun container and then make your torrent client container a “service” of the Gluetun container. Yes, I know, that sounds like some advanced-level abstraction, but it is actually extremely easy to do and it will save you from getting a nastygram from your ISP when your VPN loses connection. The MPIAA is extremely active with automated detection and processing of torrenting data, but if you set up your VPN with Gluetun, you have a perfectly effective kill switch when your VPN connection drops. And, no, the built-in killswitch on your VPN client won’t work with containers.
Seconding the other user’s post, it’s just storage. You can use it temporarily for the Plex server but I highly recommend offloading that task to a real computer.
A used Optiplex is usually the go-to because it’s low power and capable of doing the job. Just make sure it has enough RAM to handle the containers you wanna put on it.
Docker is a little bit of learning but you’ll get the hang of it. I found docker-compose to be much easier to learn. Portainer or Dockge can help by giving you a GUI, if that’s your preferred style (like me).
There was a good blog post about the real cost of storage, but I can’t find it now.
The gist was that to store 1TB of data somewhat reliably, you probably need at least:
mirrored main storage 2TB
frequent/local backup space, also at least mirrored disks 2TB + more if using a versioned backup system
remote / cold storage backup space about the same as the frequent backups
Which amounts to something like 6TB of disk for 1TB of actual data. In real life you’d probably use some other level of RAID, at least for larger amounts so it’s perhaps not as harsh, and compression can reduce the required backup space too.
I have around 130G of data in Nextcloud, and the off-site borg repo for it is about 180G. Then there’s local backups on a mirrored HDD, with the ZFS snapshots that are not yet pruned that’s maybe 200G of raw disk space. So 130G becomes 510G in my setup.
Has anyone gotten the Mediatracker scrobbler to work with Kodi? I tried and it doesn’t seem to update, at least with Seren, though I was under the impression scrobblers were addon independent.
selfhosted
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.