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.
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
Sonarr gets torrents and sends to qbittorrent, qbittorrent downloads the torrent and puts the downloaded file somewhere, sonarr then picks up that file and moves it to its final destination where jellyfin expects it
It's important to have seperate directories for unfinished torrent downloads and complete ones, and only have sonarr pick up from the completed one
you can use the same folder for unfinished downloads. I personally use a symlink as jellyfin won't pickup partial files
Back when I used Torrents instead of Usenet for sonarr, I had only the one folder, since Plex would generally pick up the library changes automatically anyway. I'd assume that Jellyfin is similar, although I don't use it enough to know for sure. These days I use only Usenet for sonarr/radarr since I'm paying for Usenet and it's excellent for automation/new content, and SABnzbd provides both incomplete and complete folders by default anyway.
I also only use Usenet, so yeah, might not be the case for torrents
And it's good to use hard links.
Can someone explain why, and what to use them for?
It basically creates a second pointer to the same inode which makes file moves instant. So instead of copying the data to a new location and deleting it from the old it points to the existing inode immediately. You can't do it across filesystems though so that's why trash guides recommends using
/data/media/tvand/data/torrentsinstead of the/tvand/downloadspaths the lsio setup suggests since docker treats top level folders as different file systems.It's mostly useful for torrents in my experience when you need to reseed stuff but also don't want to point Jellyfin/Plex to a live downloads directory for security reasons.
Op cant because he's using 2 different filesystems