I’ve got a site configured with ENV like this:
DISCOURSE_FORCE_HTTPS: true DISCOURSE_S3_ACCESS_KEY_ID: 'KEY' DISCOURSE_S3_SECRET_ACCESS_KEY: 'SECRET' DISCOURSE_BACKUP_LOCATION: 's3' DISCOURSE_ENABLE_S3_UPLOADS: true DISCOURSE_ENABLE_S3_INVENTORY: false DISCOURSE_S3_BACKUP_BUCKET: 'mybucket/backups' DISCOURSE_S3_UPLOAD_BUCKET: 'mybucket' DISCOURSE_S3_CDN_URL: 'https://mybuckets3.cdn.literatehosting.com' DISCOURSE_S3_REGION: 'us-west-1' DISCOURSE_BACKUP_WITH_UPLOADS: 'false' DISCOURSE_CDN_URL: 'https://mybucket.cdn.literatehosting.com'
It worked fine until I added the
s3 cdn url. After I added the S3 CDN, my browser started rejecting requests to the normal (not S3) CDN. I added the CDN url to
SiteSetting.content_security_policy_script_src= and then it worked again. This seems like a bug, no? I just did a restart after changes these ENV variables, not a rebuild. Do I need to do a
rake assets:precompile when I changed the CDN settings?