trash
fedilink
Apathy Tree
creator
link
fedilink
English
14M

deleted by creator

Docker is pretty easy to use, and is easy to play with either on your own system (linux or windows) or in VM guest system. The learning curve isn’t that high and Jellyfin for example has a clear set up guide for docker on their wiki.

But radarr, sonarr etc can be installed directly within linux without docker. The Servarr wiki (that these projects use officially to share information as they’re so similar) has lots of straight forward guides for set up on Linux, Windows, Mac etc as well as Docker.

I have a Linux guest VM set up with a Radarr, Sonarr etc set up, VPN and torrent set up. It was easy to do and means its network activity is all securely contained away from my host system. The tools let me set naming rules and file preferences. The library is a shared n folder in my host system, and that is included in my Jellyfin library. So all I have to do is subscribe to something i am interested in and it will just appear in my library once downloaded. The servarr tools are extremely convenient and worth looking at if you’re adding to that 30tb library over time.

Apathy Tree
creator
link
fedilink
English
04M

deleted by creator

borari
link
fedilink
English
-1
edit-2
4M

deleted by creator

Victor
link
fedilink
English
24M

everything I’ve seen for radarr, sonarr, overseerr, etc. require docker

Back when I was using Sonarr a couple years ago before that really good free tracker died, I wasn’t using docker at all. Just a systemd unit for the server and one for the web interface I believe, or maybe just the one for both. I’m on Arch.

I hope that helps.

Apathy Tree
creator
link
fedilink
English
-14M

deleted by creator

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 125 users / day
  • 420 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog