Configure an S3 compatible object storage provider for uploads

Documentation Self-Hosting
, , ,
476

I do not seem to have wiki edit permission, but I did successfully use a different provider.

OVHcloud

Service name: Object Storage

Regions correspond to data centers which are identified by a three letters code. If you don’t know where you created your bucket, check in the object storage tab in your customer portal.

DISCOURSE_USE_S3: true
DISCOURSE_S3_REGION: [data center code]
DISCOURSE_S3_ENDPOINT: https://s3.[data center code].io.cloud.ovh.net/
DISCOURSE_S3_ACCESS_KEY_ID: [key]
DISCOURSE_S3_SECRET_ACCESS_KEY: [key]
DISCOURSE_S3_BUCKET: [bucket name]
DISCOURSE_S3_BACKUP_BUCKET: [bucket name]
DISCOURSE_BACKUP_LOCATION: s3
1 Like
477

Did you make OVHcloud S3 work for uploads or just backups?

478

Initially both in my test version but I went to prod with only backups since the prod machine has a ton of space anyway.

It’s very compatible S3, but there are some things missing like lifecycle rules to delete old files or move them to cold storage which are being actively worked on by OVH. It works fine to serve files though.

So for backups I just used Discourseʼs option to delete old backups on its own.

1 Like
479

This is a really disappointing and completely unhelpful response. What exactly is the issue? Linking to a support document that changes means that no one can actually tell what the heck the “awful brokenness” mentioned in this thread here.

You mention “metadata” and that the CDN “doesn’t know about it”. What metadata? It would be helpful to know what isn’t working.