Follow

I struggled to get Mastodon working with + because the right .env.production file configuration settings eluded me. Here's what works for me:

S3_ENABLED=true
S3_BUCKET=[space name]
AWS_ACCESS_KEY_ID=[key]
AWS_SECRET_ACCESS_KEY=[key]
S3_REGION=[datacenter]
S3_PROTOCOL=https
S3_HOSTNAME=[datacenter].digitaloceanspaces.com
S3_ENDPOINT=https://[datacenter].digitaloceanspaces.com
S3_ALIAS_HOST=[space name].[datacenter].cdn.digitaloceanspaces.com

@lawremipsum I’m glad you shared! Sorry you had to fight it, I went through the same thing and did not post anything. github.com/jamesprior/mastodon is what I’m using although the values are kinda obscured.

@lawremipsum thanks for this! this was amazingly useful in wiring up our masto instance to a DO space!

to extend on it, if you're using a custom subdomain for your space then you can set S3_ALIAS_HOST to that subdomain so your media URLs include it, which is nice!

@alexis thanks! I think the custom subdomain option is new since I wrote it, so that's good to know!

Sign in to participate in the conversation
MSP Social.net

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!