From cf4ae5188811e14773fb3ec6c00a7ea24f2e0726 Mon Sep 17 00:00:00 2001 From: Thomas Urban Date: Fri, 21 Feb 2025 09:33:53 +0100 Subject: [PATCH] provide default matching expected format (#1600) After encountering issues with setting up S3 myself, I deem the default provided on `S3_ENDPOINT` as misleading. Before, I have been using a custom hostname, only, resulting in lots of warnings in the log reading `expected :endpoint to be a HTTP or HTTPS endpoint`. --- content/en/admin/optional/object-storage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/admin/optional/object-storage.md b/content/en/admin/optional/object-storage.md index f0b8dcbe..7879873b 100644 --- a/content/en/admin/optional/object-storage.md +++ b/content/en/admin/optional/object-storage.md @@ -53,8 +53,8 @@ To enable S3 storage, set the `S3_ENABLED` environment variable to `true`. - `S3_REGION` (defaults to 'us-east-1', required if using AWS S3, may not be required with other storage providers) -- `S3_ENDPOINT` (defaults to 's3..amazonaws.com', required - if not using AWS S3) +- `S3_ENDPOINT` (defaults to 'https://s3..amazonaws.com', + required if not using AWS S3) - `S3_BUCKET=mastodata` (replacing `mastodata` with the name of your bucket) - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` need to be set to