If someone wanted to dip their tires in the water of the *-arr stack, what would be some good first steps? Just to get started?
(Not asking for me, of course! Asking for my neighbor’s first cousin’s friend. He has been experimenting with dumping his DVDs and CDs to a hard drive.)
Just wanted to emphasize that the VPN is only necessary for the torrent client.
It also makes sense to run everything in containers and setup gluetun or something similar with a VPN and then point the torrent client container to the gluetun container. That way your ip can’t leak once the VPN connection fails.
The arrs shouldn’t be run through a VPN. Just have them in containers. That way the communication only takes place within the container network.
If you’re using usenet, SSL is sufficient. No need for a VPN really.
Thats fine for an easy simple install where the work is done for you but it doesnt fully help understand how it all works. Its better to learn from scratch to understand structure and how each container interacts with each other, directories, etc
They said to just get stared. I still get to completely design my entire docker.yml file to my liking but just sets up a skeleton that works for some but you can adjust it. Using yams from the start was great because I adjusted my containers many times and could restart all my containers at once. They still all run as docker and work the exact same as docker, it’s just a nice setup and restart tool.
Yeah, I get that and its fine for getting started. I guess I just took the hard route and went searching to learn it all from scratch when I started mine lol.
If someone wanted to dip their tires in the water of the *-arr stack, what would be some good first steps? Just to get started?
(Not asking for me, of course! Asking for my neighbor’s first cousin’s friend. He has been experimenting with dumping his DVDs and CDs to a hard drive.)
My friend has a VPN and runs them on his desktop Mac. He’s considering running on an old laptop or some other dedicated device
Then, Sonarr and Radarr for show and movie automation. Once you’re hooked, you’ll figure out the rest.
Just wanted to emphasize that the VPN is only necessary for the torrent client.
It also makes sense to run everything in containers and setup gluetun or something similar with a VPN and then point the torrent client container to the gluetun container. That way your ip can’t leak once the VPN connection fails.
The arrs shouldn’t be run through a VPN. Just have them in containers. That way the communication only takes place within the container network.
If you’re using usenet, SSL is sufficient. No need for a VPN really.
My neighbour’s sister’s dog started with an old PC and https://wiki.servarr.com/ or so he says…
That Trash guide is super helpful for my cousin’s neighbor’s dog-groomer’s friend!
Thanks!
Well your third cousins mailman’s dog should check out the sidebar for the community! The megathread has tons of good info
Yams! https://yams.media/
Simple install and simple to keep adding to a single docker file.
Thats fine for an easy simple install where the work is done for you but it doesnt fully help understand how it all works. Its better to learn from scratch to understand structure and how each container interacts with each other, directories, etc
They said to just get stared. I still get to completely design my entire docker.yml file to my liking but just sets up a skeleton that works for some but you can adjust it. Using yams from the start was great because I adjusted my containers many times and could restart all my containers at once. They still all run as docker and work the exact same as docker, it’s just a nice setup and restart tool.
Yeah, I get that and its fine for getting started. I guess I just took the hard route and went searching to learn it all from scratch when I started mine lol.