# Migrating settings should take GlobalSettings into account

**URL:** <https://meta.discourse.org/t/migrating-settings-should-take-globalsettings-into-account/379789>\
**Category:** Bug\
**Created:** [August 22, 2025, 4:27am UTC](https://meta.discourse.org/t/migrating-settings-should-take-globalsettings-into-account/379789 "2025-08-22T04:27:21Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [August 25, 2025, 6:29am UTC](https://meta.discourse.org/t/migrating-settings-should-take-globalsettings-into-account/379789/4 "2025-08-25T06:29:06Z")

</div>

> [@sam](#):
>
> I am not sure if GlobalSetting is loaded or is something we want to lean on, but taking a peak at
> 
> `ENV['DISCOURSE_AUTOMATIC_BACKUPS_ENABLED']`

Yes, GlobalSetting is loaded during migrations 👍

I don’t think you want to lean on a build time ENV var either? It makes it hard to separate the ENV var to discourse.conf step and the actual container deployment. In my other world (PHP/Laravel) this is seen as an anti-pattern.

---

_[View the full topic](https://meta.discourse.org/t/migrating-settings-should-take-globalsettings-into-account/379789)._