Jellyfin: Where to place /media to prevent it from being borged

[Anvil5465]

It seems like if I keep my /media folder in a Nextcloud user's files, it will be included in the borg backup. It also seems like the /media folder needs to be in the nextcloud data directory. Where should /media be stored to prevent it from being backed up? My current solution is to create a new folder in the nextcloud data directory for jellyfin, but I'm not sure if this is being backed up or not.

[szaimen]

Hi, see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host

[Anvil5465]

@szaimen Thank you. This worked. However, I am unable to delete videos through the Jellyfin interface. It says that it does not have sufficient permissions. I have given the www-data group read and write access. Should this be enough to allow Jellyfin to delete files? Or does the Jellyfin container run as a different user?

Edit: I see that in the json, NEXTCLOUD_MOUNT is not listed as writeable. I can understand why this would be the case. Is there any workaround? Not a huge deal, but it would be nice to be able to delete content in the jellyfin GUI

[szaimen]

Hm. I think the idea was that jellyfin is rather used like a viewer and editing is still done via Nextcloud. However I would accept a patch that adjusts this value.