DMed you
- Thank you :)
- I like to keep them seperate. Makes it easier to troubleshoot if some path goes haywire or what not. Also makes it easier to update one without stopping the other
- Yeah i will go through them and remove the version
DMed you
You're welcome!
After we learned that disney can kill your husband / wife and you're not even allowed to take them to court because you signed up for a disney+ trial years ago, i am more than happy for every single person that is able to rip as much of their (most of the time) shitty content
Glad you find it well-written :)
Well it isn't really that hard techznically, but you have to be really sure it actually works and that's the hard part.
You can look into "Gluetun". It is a small docker service that supports PIA. You will have to put this and the rest of the ARR stack into the same "docker network" and configure it so that radarr, etc. go through Gluetun and use it's VPN.
You can then open a terminal for the radarr container for example and run curl ipinfo.io for example to check the IP adress that container has to the outside world.
I didn't do that whole gluetun setup in quite a while so i'm not really in the position to give a proper guide on how to route your docker containers through it. But there are guides out there that will definetely help.
Testing that it's failproof would be for example run while sleep 5; do clear && curl ipinfo.io; done which shows your outside world IP for that container once per 5 seconds. Then stopping that gluetun container and look if the radarr container stops the ping and / or suddenly shows your real IP.
EDIT: found a quick readme for the gluetun container that shows how to route other containers through it
The are stack itself is so low power that you absolutely can run it on a NAS like synology for example... I mean you can run a Plex server on a NAS and it actually works so...
In my case I have it seperated. I have a NAS that does absolutely nothing else besides being a NAS. I then have my mediaserver for the are stack and jellyfin.
So that could be your Pi, and the you get an old used Synology for example.
You're right, but introducing .env files would be an extra step for each and every docker process here.
This was meant as an absolutely fundamental basic setup. If you know your way around docker you also know what to improve from those guides.
Everyone who does not know this, can get the services up and running without extra steps.
It's a fork of it specifically for jellyfin instead of Plex, so yes 👍
Nice heads up
I don't think a raspberry pi is really suitable for huge amounts of storage. Ideally you should prefer some proper NAS device that also does some proper RAID configuration.
Happy to hear!
I updated the guides to include a link to my next guide: Jellyfin + Jellyseer in junction with sonarr / radarr. Make sure to refresh the page :)
I have tried it like that before writing the guide and it didn't cause issues. But yes, if it does one could simply mount the whole base folder and navigate from there