Comment

Comment on Someone help me understand the sonarr to jellyfin workflow

plantsmakemehappy@lemmy.world ⁨1⁩ ⁨week⁩ ago

If the torrents are still seeding when the import in arrs happens, it would copy the file(s) to your media folder so you’d have two copies now. If the torrent is done seeding and, I think if you have completed download handling enabled, it’ll do a move instead so you’d end up with only one copy.

Ideally though you want a hardlink compatible setup but from what you said you do not.

Jellyfin just monitors your media folder which is managed by the arrs.

source

Sort:hotnew top

hedgehog@ttrpg.network ⁨1⁩ ⁨week⁩ ago
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.

source
- StarvingMartist@sh.itjust.works ⁨1⁩ ⁨week⁩ ago
  Wouldn’t symlinks essentially “copy” the file? I need it to be deleted, so it doesn’t fill up the drive
  
  source
  - felbane@lemmy.world ⁨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.
    
    source