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
as always, the answer is "it depends" - everyone has their own unique flavor of *arr stack with different components. Breaking it down, everything revolves around the core apps:
These apps do the majority of the hard work of going from eg. "I want this movie" to "this movie file is now downloaded and placed into a subdirectory on my NAS or storage somewhere"
Realistically, all you need to get started is a download client (usenet, torrent client, whatever - the most popular choice is qbittorrent-nox or an equivalent docker container), your *arr app(s) of choice, and a way to consume and share the media you've now downloaded to your NAS or server (plex, jellyfin, stash, audiobookshelf, VLC, etc)
For consuming media, here's a non-comprehensive list that most people will recommend at least one thing from:
The rest of the *arr ecosystem serves as a way to automate this core idea or fix issues with that automation. An example from my own homelab:
Not all of these will be useful to you, and you'll likely find others that are more useful for your situation. Like I mentioned, everyone's *arr stack is different and unique.
My recommendation: start with an *arr or two, configarr (optional but really recommended - hard to set up but once you do you're good forever), prowlarr (optional but you'll thank yourself later if you ever get into this and end up with more *arrs), and unpackerr (really do recommend this one) and go from there.
I'd also add:
Sometimes you just want to send someone a random file without needing to create an account for them and walking them through installing an app. You can use Filebrowser to generate a link that they can access to browse that specific file/directory without credentials. You can set these links to timeout after minutes/hours/days/never.
Useful to have a link to all of your services in a portable and shareable form. Very customizable and useful for most homelab assets.
Gotta say this one's probably more helpful than any guide I could've found online. This does give a very clear idea of what exactly it is I'm dealing with, I'll [try to] keep all these points in mind while I try to manifest a makeshift first attempt. Thanks a ton for all this insight!
For anyone interested in the configarr config I use, here you go. It's somewhat customized to my taste (especially dubs > subs for anime) and there's likely an issue or inconsistency or two in it that someone more familiar might be able to spot, but it works pretty well and I'd say it's a good starting point if you just want to get going.
Note that it's a kubernetes ConfigMap but it's not hard to pull the relevant info into docker for your own needs.