I followed the following setup in my staging/test server in web_only.yml. But it seems that the backups are still going in the latest discourse? Seems that it is ignoring the environment variable.
## Staging server specific settings
DISCOURSE_AUTOMATIC_BACKUPS_ENABLED: false
DISCOURSE_LOGIN_REQUIRED: true
DISCOURSE_DISABLE_EMAILS: 'yes'
DISCOURSE_S3_DISABLE_CLEANUP: true
DISCOURSE_ALLOW_RESTORE: true
RGJ
(Richard - Communiteq)
December 1, 2025, 7:09pm
2
The automatic_backups_enabled setting has been removed in August…
committed 06:56AM - 11 Aug 25 UTC
We're removing the automatic_backups_enabled toggle and depending solely on the … backup_frequency value. This PR replaces the setting and adds a migration for any forum that has automatic_backups_enabled disabled.
Use backup_frequency (DISCOURSE_BACKUP_FREQUENCY: 0) instead to disable backups entirely.
1 Like
Thanks for the solution.
I also just updated the Wiki here:
There are several tricks that can help when you are setting up a staging server.
What is a staging server?
A staging server is essentially a clone of a production site. It also resides on a server, and functions identically. It runs inside a Docker container, just as a normal Discourse site does.
It exists to give you a place to try risky things out, or to trial things that you cannot easily hide from your users. It is very useful for trialling adverts using the Discourse Advertising Plugin (A…
It was still referring to the old method.
2 Likes
system
(system)
Closed
December 31, 2025, 7:59pm
4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.