Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I hate how fragmented they are. I've given up on various guides out there for 'setting up the arr stack' because of getting bogged down in since miniature detail that, IMHO, shouldn't even be a thing. I get that hosting seperate services has advantages. But the disadvantage of giving up on the whole thing because you have to sort out networking and file permission issues between the service that downloads video files over an hour long and the service that downloads video files under an hour outweighs those advantages.
Spoiler: I am deeply into the arr "ecosystem" and love the shit out of it.
I think I finally understand Linux fans. Yes it's confusing for new people, but because I'm so into the weeds on this stuff I love how much choice I have. And if one of the projects doesn't have what we want, someone makes a fork.
To point: you really only need Sonarr and Radarr. Get those set up and working how you like. I recommend the Trash Guides. Once that's working how you like, get Prowlarr for easy management of your usenet and torrent indexers. Most people should stop there.
You're not alone. It's super frustrating when things don't work and you have to search through 4 apps to figure out what is wrong. This architecture makes the whole setup brittle.
Fortunately, there are all in one alternatives to the arr stack. I found a couple, but I think Cinephage is the most mature.
Do you know how it compares to bobarr?
You said it's the most mature, but it's only about 2 months old and coded partially with AI.
I'm interested in this but paranoid about security, and don't know how much I can trust something newish they also has some code the developer might not understand.
Oh thanks, I hadn't even noticed that. I did some research into *arr alternatives a few weeks ago. I found 3 and this one looked like it had the most features. I will look up the other two contenders again then.
Let me know if you find what they are - I'm interested in a solution like this anyhow too.
Found them:
The first one seems to be the most trust worthy, as it's nearly a year old and has sponsorship apparently from Digital Ocean. Might try that one. The UI isn't as pretty but it still seems much simpler than managing an Aar stack.
The second one is also young, but programmed mostly in a language I hadn't heard about (Elixer).
Huh. That sounds overly complicated. I just link everything with my torrent client. Tracker (prowlarr) into media managers (sonarr/radarr) into torrent client. That's it.
I have jellyseer in there too but that's a separate service that just works. The core stack is the other paragraph.
Everything is installed in my local server using the install script, no docker.
I think avoiding containers is the way I'm going to go on my next attempt. I'll still have to put it in an lxc or a VM on my proxmox, but all in one will hopefully reduce some problems. The sonarr/radarr split was what I was referring to with the above or below an hour comment.
What problems did you have? I just put the services I wanted in a compose file, configured sonarr/radarr to use prowlarr and my torrent client and done.
Later I added lidarr and readarr but ended up removing the last one. I found it easy enough, and the modularity makes it easy to use only what you need.
Just in case you wanna try again with readarr, after all the little drama and the main app being unmaintained, there’s 2 forks which are maintained and work pretty well
I’ve successfully been running bookshelf for a bit now, after the original stopped working for me completely.
I'll keep them in mind, but I stopped using readarr because the sonarr/radarr approach didn't work for me for books. I read individual books more than subscribe to everything an author does, and manually downloading them is not really a problem.
Ikr like... Give me a docker compose file and tell me what env vars need to be set to what. Why is it so complicated?
Completely agree. If the *arr stack had environment variables for key settings, I'm sure we'd see Compose files instead of TRaSH how-to guides. It's frustrating everything is configured in the GUI.
Either you misconfigured something or you are very new to this.
Keep it up.
As for good guides: Trash-guides
They provide a very in depth set-up that works really well.
The only thing you'll need after this, is a source for the files.