I had this problem before and decided that I was crazy, confused, or the database on the site was suspect, but this is on a brand new site. Also, I was on Digital Ocean spaces, so I thought it might be a problem somehow.
I’m trying again to figure out how to keep images on AWS S3 like I think the Big Boys do.
Here’s what I have in the
DISCOURSE_S3_ACCESS_KEY_ID: 'key' DISCOURSE_S3_SECRET_ACCESS_KEY: 'lock' DISCOURSE_BACKUP_LOCATION: 's3' DISCOURSE_S3_BUCKET: 'lc-xyz' DISCOURSE_S3_BUCKET_NAME: 'lc-xyz' DISCOURSE_S3_BACKUP_BUCKET: 'lc-xyz/backups' DISCOURSE_S3_UPLOAD_BUCKET: 'lc-xyz/uploads' DISCOURSE_S3_CDN_URL: 'https://lc-rbx.s3.amazonaws.com'
When I include the
s3 cdn url the site breaks because all of the links to the assets are on S3 like
Because if you define
s3 cdn url Discourse looks for the assets on the s3_cdn_url.
I did a rebuild, but the assets are still missing. I can do a
Is there an
after_bundling_assets stanza that I could add that to? (I know about
after_bundle_exec, but don’t know if those would work.)
Do assets get produced some other time? (It would seem like when themes get modified assets would change.)
If I also had a “push CDN like normal”, would that keep this from happening?
Is there some best practice that I’m missing?