starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[PR #8107] Move transcodes to be under CachePath #11619

New Issue
Closed
opened 2026-02-07 06:41:38 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 06:41:38 +03:00
Owner
Copy Link

Original Pull Request: https://github.com/jellyfin/jellyfin/pull/8107

State: closed
Merged: Yes

Changes
Move transcodes to be under CachePath instead of ProgramDataPath.

Since transcodes are ephemeral (they're cleaned up periodically and recreated if they don't exist), they're more like cache data than program data. Systems can (and oftentimes do) have the cache directory on a different disk, use a different type of file system, or have a different backup policy for the cache path because it contains ephemeral data.

Issues
This PR doesn't exactly solve the following issues, but it is related to them, as it changes jellyfin to use a more appropriate path for these temporary files which makes it more likely that the system will be configured to handle this data more appropriately avoiding these issues:
https://github.com/jellyfin/jellyfin/issues/4893
https://github.com/jellyfin/jellyfin/issues/3929

**Original Pull Request:** https://github.com/jellyfin/jellyfin/pull/8107 **State:** closed **Merged:** Yes --- <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** Move transcodes to be under CachePath instead of ProgramDataPath. Since transcodes are ephemeral (they're cleaned up periodically and recreated if they don't exist), they're more like cache data than program data. Systems can (and oftentimes do) have the cache directory on a different disk, use a different type of file system, or have a different backup policy for the cache path because it contains ephemeral data. **Issues** This PR doesn't exactly solve the following issues, but it is related to them, as it changes jellyfin to use a more appropriate path for these temporary files which makes it more likely that the system will be configured to handle this data more appropriately avoiding these issues: https://github.com/jellyfin/jellyfin/issues/4893 https://github.com/jellyfin/jellyfin/issues/3929
OVERLORD added the pull-request label 2026-02-07 06:41:38 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#11619
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?