Remove it from app.yml and rebuild.
Wich row have I to comment to disable s3 upload?
DISCOURSE_DEVELOPER_EMAILS: ‘help@forumrossoblu.org’
DISCOURSE_S3_REGION: eu-central-1
DISCOURSE_S3_ACCESS_KEY_ID: *****
DISCOURSE_S3_SECRET_ACCESS_KEY:** *
DISCOURSE_S3_BUCKET: bucketname
DISCOURSE_S3_BACKUP_BUCKET: bucket backup name
DISCOURSE_BACKUP_LOCATION: s3
DISCOURSE_S3_CDN_URL: “”
My guess is this one
This solved my problem.
only have one issue: the disk space has been significantly reduced after the restore. I had already performed a restore in the past, but this issue did not occur then. It seems there’s a problem on the database after the restore
Discourse keeps a backup schema so it can roll back when a restore goes bad.
You can go into your Postgres and issue drop schema backup cascade;
If you don’t know how to do that you shouldn’t probably be doing it.
I’ll probably ask it to an expert friend![]()
Thank you so much, it works.
