Honor configurable cache size with LRU eviction
This commit is contained in:
@@ -67,6 +67,19 @@ The fixed source blacklist is:
|
||||
|
||||
Client error reports never modify this list.
|
||||
|
||||
## Cache resizing
|
||||
|
||||
`CACHE_MAX_BYTES` is the worker's configurable LRU limit. After changing it and
|
||||
restarting the container:
|
||||
|
||||
- A smaller value evicts the oldest unlocked entries until usage fits.
|
||||
- A larger value immediately makes the additional capacity available for
|
||||
background population, up to the size of the mounted cache filesystem.
|
||||
|
||||
The host filesystem is deliberately separate from application logic. Enlarge or
|
||||
shrink its preallocated image during infrastructure maintenance, then set the
|
||||
matching `CACHE_MAX_BYTES` value in Coolify.
|
||||
|
||||
## Playback locking
|
||||
|
||||
- An active movie locks that movie.
|
||||
|
||||
Reference in New Issue
Block a user