From 1d406be66d3aae86e85a78ecee29ed109619f97f Mon Sep 17 00:00:00 2001
From: Travis Ralston <travpc@gmail.com>
Date: Sat, 1 Aug 2020 15:32:25 -0600
Subject: [PATCH] Clarify how minBytes is meant to work

---
 CHANGELOG.md       | 1 +
 config.sample.yaml | 5 ++++-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4bbcc8dc..4dbfee63 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -20,6 +20,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 * Remove deprecated support for restricting uploads to certain mime types.
 * Remove deprecated support for `forUploads`.
+* Clarified what `uploads.minBytes` is intended to be used for.
 
 ### Fixed
 
diff --git a/config.sample.yaml b/config.sample.yaml
index 81a634d0..57ec20a4 100644
--- a/config.sample.yaml
+++ b/config.sample.yaml
@@ -197,7 +197,10 @@ archiving:
 uploads:
   maxBytes: 104857600 # 100MB default, 0 to disable
 
-  # The minimum number of bytes to let people upload
+  # The minimum number of bytes to let people upload. This is recommended to be non-zero to
+  # ensure that the "cost" of running the media repo is worthwhile - small file uploads tend
+  # to waste more CPU and database resources than small files, thus a default of 100 bytes
+  # is applied here as an approximate break-even point.
   minBytes: 100 # 100 bytes by default
 
   # The number of bytes to claim as the maximum size for uploads for the limits API. If this
-- 
GitLab