Cómo usar el servidor de almacenamiento MinIO para tu instancia de Discourse

[teward (Thomas Ward)]

Utilizing MinIO server for S3 compatible object storage

MinIO is an S3-compatible object storage server solution that is cloud-native by default but easy to deploy on on-prem servers or VPSes or cloud servers for your use as an alternative to Amazon AWS S3 or other systems, and is compatible with Discourse when configured right.

This section presupposes that the following are true in your environment:

1. You have a fully configured MinIO server instance
2. You have Domain Support enabled in the MinIO configuration
3. You have DNS configuration properly set up for MinIO so that bucket subdomains properly resolve to the MinIO server
4. The bucket discourse-data exists on the MinIO server and has a “public” policy set on it
5. The bucket discourse-backups exists on the MinIO server and is a private bucket for uploads to be put into (and not publicly reachable - the default policy for new buckets)
6. Your S3 CDN URL is a properly configured CDN pointing to the bucket and cache requests, as stated earlier in this document.

If you have all of the above requirements available, then you should be good to go.

An example configuration would be like this:

DISCOURSE_USE_S3: true
DISCOURSE_S3_REGION: anything
DISCOURSE_S3_ENDPOINT: https://minio.example.com
DISCOURSE_S3_ACCESS_KEY_ID: myaccesskey
DISCOURSE_S3_SECRET_ACCESS_KEY: mysecretkey
DISCOURSE_S3_CDN_URL: https://discourse-data-cdn.example.com
DISCOURSE_S3_BUCKET: discourse-data
DISCOURSE_S3_BACKUP_BUCKET: discourse-backups
DISCOURSE_BACKUP_LOCATION: s3

This will provide you with a basic MinIO configuration with a MinIO server in place of Amazon S3.

[Falco]

It’s great to know that MinIO now works fine with subdomain style buckets and is again compatible with Discourse.

Can you edit the Using Object Storage for Uploads (S3 & Clones) wiki to include MinIO instructions?

[teward (Thomas Ward)]

It’s worked with both subdomain AND path style buckets for a while. However, the DNS configuration component is the most painful component - it needs special wildcard DNS rules to work, or a customized DNS server that is actively aware of all actual buckets or not. I’ve done that in bind9 with wildcard zones, but doing it in Cloudflare or others and the subdomain style bits barf hard.

IF you think the above is suitable to be in that section, I’ll be happy to. But it’ll include that ‘caveats’ section - and I’d appreciate any exits/reviews you’d like me to make first for wording, etc. (And note I didn’t include a CDN URL 'cause I don’t have a CDN in my deployment (because $$$ is not something I can experiment with).

[Falco]

@teward

However, the DNS configuration component is the most painful component - it needs special wildcard DNS rules to work, or a customized DNS server that is actively aware of all actual buckets or not.

Users who run MinIO just for Discourse can also create the DNS entries for the 2 Discourse buckets manually too right?

The caveat in this topic should be enough. Configuring MinIO is completely out of scope for this forum, but given a working MinIO getting Discourse to use is a valid use case.

[teward (Thomas Ward)]

@Falco

Users who run MinIO just for Discourse can also create the DNS entries for the 2 Discourse buckets manually too right?

Correct, but as you said config is out of scope, so I simply will state that the bucket subdomain paths have to resolve (and will leave DNS config to ${ADMINS} of the instance)

[teward (Thomas Ward)]

@Falco

given a working MinIO getting Discourse to use is a valid use case.

Yep, and I"ve edited the wiki accordingly. However, MinIO doesn’t (to my knowledge) run a cloud service so I left the ‘Service Name’ in the wiki TOC at the beginning blank, adjust accordingly if you wish.

[Falco]

Awesome! Thanks for the contribution!

[teward (Thomas Ward)]

You’re welcome!

I also tweaked it, Provider is Self-hosted but the MinIO section is still linked to. That should solve the fact they don’t have a cloud provided solution that I could find at the moment. (You can close this thread now if you wish since it’s integrated into the wiki post)

[teward (Thomas Ward)]

Also discovered (thank you open source code and decent documentation for MinIO!) that CORS is already by default on all MinIO HTTP action verbs - so no need to install the CORS rules, they’re already present. Also updated the self-hosted minio section as well, plus some grammar tweaks.

Thanks to @Falco for some help tracing the issue I had noticed during app build / rebuild time for this, and for the base guidance on CDN config with StackPath (because I wanted a fully functional test, and have StackPath CDN for something else anyways so using the CDN stack verified everything worked!)

[ceelian (Christian)]

No entiendo cómo configurar el estilo de ruta de fuerza. Cuando configuro la versión 2.6.8 con minio a través de la configuración de S3, siempre antepone el nombre del bucket al punto final de s3, donde debería añadirlo como ruta después del punto final de s3.

También parece, por la muestra de configuración en github, que la opción s3_force_path_style ha sido eliminada. ¿Me estoy perdiendo algo? Gracias.

[teward (Thomas Ward)]

@ceelian

Discourse usa el modo DNS, no el modo de ruta, para S3. Ha sido así DURANTE MUCHO TIEMPO, por eso no especifico nada sobre el modo de ruta en el manual o en la página del manual de almacenamiento S3. También deberías aprender a crear nuevos hilos en lugar de revivir un hilo antiguo para algo no relacionado.

[ceelian (Christian)]

@teward Gracias por tus comentarios. Disculpa por revivir el hilo, estoy acostumbrado a la forma de escribir de los issues de GitHub Comenzaré un nuevo hilo sobre cómo podemos usar discourse S3 en modo de ruta.

[teward (Thomas Ward)]

@ceelian

Comenzaré un nuevo hilo sobre cómo podemos usar Discourse S3 en modo de ruta.

Para tu información: no puedes. No creo que el modo de ruta sea compatible, por eso esa opción para forzar el modo de ruta para Discourse ha desaparecido. También es por eso que la sección que originalmente agregué a la página de cómo configurar un proveedor de almacenamiento de objetos compatible con S3 ahora dice bajo advertencias y requisitos:

2. Tienes habilitado el soporte de dominio en la configuración de MinIO, para URL de bucket dirigidas por dominio. Esto es obligatorio y no es una opción, no hay soporte basado en rutas en Discourse para rutas de bucket.

Hace mucho tiempo, cuando trabajé por primera vez con Discourse, tenían esa opción, luego la eliminaron y tuve que dejar de usar MinIO como backend. AHORA, dado que hay documentación en MinIO sobre cómo hacer que el modo DNS funcione (es decir, rutas bucket[.]server[.]com ahora como lo hace S3), funciona cuando se configura MinIO correctamente. (Gracias al personal/moderadores/sistema por aumentar mi nivel de confianza para editar el wiki ahora).

[ceelian (Christian)]

¡Gracias por la aclaración y la pista sobre cómo resolver el problema!