S3 broken on Scaleway
Scaleway has a S3 compatible object storage service (https://www.scaleway.com/object-storage/)
I filled everything in according to the comments:
# Configure S3 support if desired.
# The public S3 endpoint is different depending on region and provider,
# consult your S3 provider's documentation for details on what to use.
#
config :pleroma, Pleroma.Uploaders.S3,
bucket: "[bucket]",
public_endpoint: "https://[bucket].s3.nl-ams.scw.cloud"
# Configure S3 credentials:
config :ex_aws, :s3,
access_key_id: "SCW0D1FCNE90KH6CCA79",
secret_access_key: "a2443bc0-2957-4e2e-9c80-a95481ce260c",
region: "nl-ams",
scheme: "https://"
#
# For using third-party S3 clones like wasabi, also do:
config :ex_aws, :s3,
host: "s3.nl-ams.scw.cloud"
There is a slight problem: Pleroma generates public urls by using {public_endpoint}/{bucket}/{filepath}
Scaleway doesn't use the bucket path though, but as you can see, it is using a subdomain.
Now I have to decide: support upload but no download/view, or keep bucket empty, make viewing possible but breaking upload
Edited by Criss