this post was submitted on 24 Mar 2025
95 points (96.1% liked)

Selfhosted

45337 readers
623 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:

  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!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
95
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
[–] hedgehog@ttrpg.network 3 points 1 week ago (2 children)

Is there a way to use symlinks instead? I’d think it would be possible, even with Docker - it would just require the torrent directory to be mounted read-only in the same location in every Docker container that had symlinks to files on it.

[–] InverseParallax@lemmy.world 2 points 1 week ago

That's not something they natively support, it's hard links or a copy.

[–] StarvingMartist@sh.itjust.works 2 points 1 week ago (1 children)

Wouldn't symlinks essentially "copy" the file? I need it to be deleted, so it doesn't fill up the drive

[–] felbane@lemmy.world 4 points 1 week ago* (last edited 1 week ago)

No. Symlinks and hardlinks are two approaches to creating a "pointer to a file." They are quite different in implementation, but at the high level:

  • Symlinks can point to other filesystems, hardlinks only work on the same filesystem.
  • You can delete the target of a symlink (or even create one that points at nothing), but a hardlink always points to a real file.

In both cases, the only additional data used is the metadata used for the link itself. The contents of the file on disk are not copied.