upstream/nextcloud
1
0
Fork 0
mirror of https://github.com/nextcloud/server.git synced 2026-06-25 08:31:11 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 13

docs(config): clarify metadata and conversion file size limits

Browse source 
- correct unit for metadata_max_filesize to match implementation (MiB)
- wording/clarity including resource impact


Signed-off-by: Josh <josh.t.richards@gmail.com>
This commit is contained in:
Josh 2026-06-20 09:51:16 -04:00 committed by GitHub
parent bd6995dff9
commit 68a0a79bbf
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 13 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
config/config.sample.php
View file

@ -1602,20 +1602,27 @@ $CONFIG = [
],
/**
* Maximum file size for metadata generation.
* If a file exceeds this size, metadata generation will be skipped.
* Maximum file size for file metadata generation.
*
* NOTE: memory equivalent to this size will be used for metadata generation.
* Files larger than this limit will be skipped.
*
* Default: 256 megabytes.
* This limit helps bound resource usage during metadata generation. Actual
* resource usage depends on the active metadata providers and how they
* process files. As a rough guide, memory usage may scale with file size.
*
* Default: 256 MiB.
*/
'metadata_max_filesize' => 256,
/**
* Maximum file size for file conversion.
* If a file exceeds this size, the file will not be converted.
*
* Default: 100 MiB
* Files larger than this limit will be skipped.
*
* Raising this limit may increase conversion time, resource usage, and the
* risk of timeouts or conversion failures depending on the provider.
*
* Default: 100 MiB.
*/
'max_file_conversion_filesize' => 100,