Hi @da2ce7 @WarmBeer, I've just realised that we cannot update the settings when we use the environment variable instead of the config.toml file.

If we use the env var there is no file. The main problem is that the config env var was added as a read-only way to inject configuration.

From my point of view, we should move to the database or a different file the settings we want to allow the admin to change via the admin panel. If we want the admin to change everything then we have to make some changes because, for example, you cannot change the app port or IP without restarting the socket (gracefully).

For the time being, I would only allow changing these settings:

[website]
name = "Torrust"

[auth]
email_on_signup = "Optional"

[mail]
email_verification_enabled = false

And I would move them to a new table in the database (with default values).

If we do not want to make those changes now, I would totally disable the ability to update the settings from the control panel.

ACK 655f631