Definir enlaces DISCOURSE_S3_CDN_URL a activos en la URL de CDN de S3

[eatcodetravel (Orlando Del Aguila)]

Supongo que esto se debe a que te falta DISCOURSE_CDN_URL. En nuestra configuración lo tenemos así:

DISCOURSE_CDN_URL: 'https://d16zv78c963s69.cloudfront.net' # esto apunta al servidor
DISCOURSE_S3_CDN_URL: 'https://community-cdn-prod.debtcollective.org' # esto apunta al bucket de S3

Las hojas de estilo se obtienen del servidor, por lo que usan DISCOURSE_CDN_URL. Los archivos de JavaScript se suben al bucket de S3 y usan DISCOURSE_S3_CDN_URL. @Falco me lo explicó aquí.

Assets not serving from CDN in latest update

If you inspect this page you will see that we we have two different Cloudfront URLs, so we use what I said above, two distributions, one for the normal CDN and another for S3. The problem from the title of the OP is this: CSS come from the app and JS from S3. You need a CDN that is aware of where every single asset is coming from and can reach the necessary place or two CDNs. That is why we have two different settings after all.