From 83a6799f0d75c2ea9436c36307f8446156a05f5c Mon Sep 17 00:00:00 2001 From: Tom Richards Date: Tue, 19 Dec 2023 09:42:17 +0000 Subject: [PATCH] improve 'running locally' documentation to reference queue-based ingestion Co-authored-by: David Blatcher <30567854+dblatcher@users.noreply.github.com> --- docs/02-running/01-running-locally.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/02-running/01-running-locally.md b/docs/02-running/01-running-locally.md index 7ad7c0f15f..39bf725a37 100644 --- a/docs/02-running/01-running-locally.md +++ b/docs/02-running/01-running-locally.md @@ -59,7 +59,8 @@ If you haven't used the `--with-local-auth` flag, you'll begin a Google authenti If you have used the `--no-auth` flag you'll be signed in automatically as John Doe (with no oauth flow) and will have ALL permissions. -Note that there's currently a 20MB limit per file on uploads to image-loader (see `client_max_body_size` in nginx mappings). +Note that there's currently a 20MB limit per file on direct/legacy uploads to image-loader (see `client_max_body_size` in nginx mappings). Theoretically you could upload such large files directly to the S3watcher bucket with something like `aws s3 cp --endpoint http://localhost:4576 ...`. +No such limit applies to the queue-based ingestion (see https://github.com/guardian/grid/pull/4201), which is the default for a fresh local setup. ## Cerebro