hedgedoc/docs/content/references/config/media/s3.md
Erik Michelson 157a0fe278 refactor(media): store filenames, use pre-signed s3/azure URLs, UUIDs
Signed-off-by: Erik Michelson <github@erik.michelson.eu>
2024-09-12 14:49:17 +02:00

1.3 KiB

S3-compatible

You can use Amazon S3 or any other S3-compatible storage (like MinIO or Ceph Object Gateway) to handle your image uploads in HedgeDoc.

Your S3 bucket must be configured to be writeable.

You just add the following lines to your configuration:
(with the appropriate substitution for <ACCESS_KEY>, <SECRET_KEY>, <BUCKET>, <REGION>, and <ENDPOINT> of course)

HD_MEDIA_BACKEND="s3"
HD_MEDIA_BACKEND_S3_ACCESS_KEY="<ACCESS_KEY>"
HD_MEDIA_BACKEND_S3_SECRET_KEY="<SECRET_KEY>"
HD_MEDIA_BACKEND_S3_BUCKET="<BUCKET>"
HD_MEDIA_BACKEND_S3_ENDPOINT="<ENDPOINT>"
HD_MEDIA_BACKEND_S3_REGION="<REGION>"
HD_MEDIA_BACKEND_S3_PATH_STYLE="<true|false>"

<ENDPOINT> should be an URL and contain the protocol, the domain and if necessary the port. For example: https://s3.example.org or http://s3.example.org:9000

<PATH_STYLE> should be set to true if you are using a S3-compatible storage like MinIO that uses path-style URLs.

If you use Amazon S3, <ENDPOINT> should contain your Amazon Region. For example: If your Amazon Region is us-east-2,your endpoint <ENDPOINT> should be https://s3.us-east-2.amazonaws.com.