Minio instead of S3?

[tophee (Christoph)]

Has anyone tried to use minio instead of S3 storage?

MinIO | Object Storage for AI

Minio is a distributed object storage server compatible with Amazon S3, but I don’t know what that means in relation to discourse…

[david (David Taylor)]

@tophee

I don’t know what that means in relation to discourse

I think it means that it won’t work, at the moment:

Extend S3 configuration for other s3 API compatible cloud storage solutions

It would be great to have an extra field host and set region optional to allow other S3 API compatible services to work with discourse for backup and files storage. Update:

[rishabh]

As of today, two more S3 compatible alternatives can be used:

1. DigitalOcean Spaces

(Superseded) Set up backup and image uploads to DigitalOcean Spaces

This topic is superseded by Configure an S3 compatible object storage provider for uploads.

2. Minio S3

https://meta.discourse.org/t/setting-up-backup-and-image-uploads-to-minio-s3/95123

[noel]

Just wanted to check for the settings page in our admin page, under S3, would that only be applicable to AWS S3?

[md-misko]

No, see here

Configure an S3 compatible object storage provider for uploads

This topic covers how to configure some common S3 compatible Object Storage providers (S3 clones). See Set up file and image uploads to S3 for more details about Amazon AWS S3 configuration, which is officially supported and used internally by Discourse for our hosting services. Provider Service Name Works with Discourse? Amazon AWS S3 Yes Digital Ocean Spaces Yes Linode Object Storage Yes Google Cloud Storage Yes Scaleway Object Storage Yes Vultr Obj…

[noel]

Thanks @md-misko, just to be sure we are talking about the same things, I was referring to this page. But of course, I can always go the manual way with adding the configurations as stated in the link you provided.

[md-misko]

@noel

just to be sure we are talking about the same things, I was referring to this page.

Yes, those are the same S3 settings, but it is preferable to set them directly in app.yml. This way they will be shadowed (i.e. not visible in Web UI) which will prevent other admins to change them inadvertently.

Please use caution when dealing with S3 (use staging environment to test extensively), as this is advanced configuration and cannot be reverted easily.

[noel]

Thanks a ton @md-misko