Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't allow to update settings #221

Merged
merged 1 commit into from
Jun 26, 2023
Merged

Don't allow to update settings #221

merged 1 commit into from
Jun 26, 2023

Conversation

josecelano
Copy link
Member

Without restarting the application. This feature was using the config.toml file. That approach is not good for theses reasons:

  • If you use env vars to inject the settings, there is no config.toml file.
  • In dockerized (clouds) envs it's harder to mount a file than injecting env vars. Sometimes it's only allowed to mount a single file.

Without restarting the application. This feature was using the `config.toml` file. That approach is not good for theses reasons:

- If you use env vars to inject the settings, there is no `config.toml` file.
- In dockerized (clouds) envs it's harder to mount a file than injecting env vars. Sometimes it's only allowed to mount a single file.
@josecelano josecelano linked an issue Jun 26, 2023 that may be closed by this pull request
@josecelano josecelano merged commit c687aa3 into torrust:develop Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Configuration is read-only when env var is used
1 participant