Selfhosted

45271 readers

1645 users here now

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!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Someone help me understand the sonarr to jellyfin workflow (sh.itjust.works)

submitted 1 week ago by StarvingMartist@sh.itjust.works to c/selfhosted@lemmy.world

37 comments fedilink hide all child comments

So I've got jellyfin all set up, but I'm having some issues with files downloading from qbittorrent and Knowing exactly how and when they get moved over, either the sonar or jellyfin repository, whichever is the final destination. This is important because my torrenting drive is separate from my media drive. I have noticed some shows and files staying on my torrenting drive while others go over to the media drive. And I'm and to figure out where the issue might be that's causing this, I think I need a refresher on exactly how and when these files are supposed to be moved over. Since I can't find any sort of documentation inside the apps.

Can anybody explain this to me like super simply? I just took an edible and it's starting to kick in, but I still want to figure this out. Thanks y'all!

you are viewing a single comment's thread
view the rest of the comments

[–] Elkenders@feddit.uk 5 points 1 week ago (2 children)

And it's good to use hard links.

[–] trevor@lemmy.blahaj.zone 1 points 3 days ago (1 children)

Can someone explain why, and what to use them for?

[–] lucid@lemmy.dbzer0.com 1 points 3 days ago

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/tv and /data/torrents instead of the /tv and /downloads paths 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.

[–] Wrrzag@lemmy.ml 3 points 6 days ago

Op cant because he's using 2 different filesystems