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 B…

Yep sorry that was a typo just in my previous post. DISCOURSE_S3_BACKUP_BUCKET doesn’t set s3_bucket in GlobalSetting for me. I’m not sure how you’re running that rake task without setting DISCOURSE_S3_BUCKET. I really appreciate your help btw and realise this isn’t your problem to solve, so thanks…

No worries is not an issue. I forgot to mention we also define USE_DB_S3_CONFIG: true in our app.yml file. https://github.com/debtcollective/infra/blob/master/modules/services/discourse/web.yml#L32 And I think you are right since this changes the behaviour of how S3 buckets get defined ( discourse/l…

Dear @eatcodetravel thanks for your great post. i am trying to set up cloudfront as you. Should i upload asset folder to my S3 bucket or will it be automatically. What will be happen after a discourse update ? Should i upload theme again if it will not be automatically. thank you.

Of course. def ensure_s3_configured! unless GlobalSetting.use_s3? || use_db_s3_config STDERR.puts "ERROR: Ensure S3 is configured in config/discourse.conf or environment vars" exit 1 end end use_db_s3_config is saving you from having to set that extra variable. That must be a bug in gl…

Irrespective of a bug in global_setting.rb I’m still seeing an issue where Discourse is looking for assets in their usual place and not on my S3 CDN, even though I’ve declared all my variables and DISCOURSE_ENABLE_S3_UPLOADS is set to true.

There’s a task for this bundle exec rake uploads:migrate_to_s3 . Once you have configured your buckets you should run that task to move uploads to s3. S3/CDN has changed in the recent few months and documentation is not up to date, so make sure you backup and prepare in case something goes wrong. W…

I guess this is because you are missing DISCOURSE_CDN_URL. We have it like this in our config DISCOURSE_CDN_URL: 'https://d16zv78c963s69.cloudfront.net' # this points to the server DISCOURSE_S3_CDN_URL: 'https://community-cdn-prod.debtcollective.org' # this points to S3 bucket Stylesheets are fetc…

Yep I saw that. I’ve set DISCOURSE_CDN_URL but I still get the same issue. However I’m tired so maybe I missed something with all the messing around. Will pick this back up tomorrow. Thanks for the help.

Will this upload both upload files as images and assets as js files to S3? And should i use a cloudfront url or S3 is enough ? thanks for you help.

bundle exec rake uploads:migrate_to_s3 will upload only attachments to S3, this task needs to be run once. After you enable S3 new uploads will be saved in the S3 buckets. To upload assets you need to use bundle exec rake s3:upload_assets and this needs to run after every rebuild/upgrade.

Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL

Product Support

riking (Kane York) March 23, 2020, 9:20pm 40

Nope, the environment variables provide an extra way to configure this stuff, e.g. before you have access to the admin panel.

Topic		Replies	Views
Unable to setup S3 bucket Self-hosting uploads , s3	11	682	January 12, 2025
Rake uploads:migrate_to_s3 fails because DISCOURSE_S3_CDN_URL env var is empty Self-hosting	1	779	September 27, 2019
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	1248	December 30, 2025
Assets not serving from CDN in latest update Product Support	16	2053	February 7, 2020
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	267	53706	September 15, 2026

Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL

Related topics