Content
View differences
Updated by Markus Kahl over 1 year ago
**As** an OpenProject system administrator
**I want to** be able to change certain configurations at runtime
**so that** I can update them without requiring a restart.
**Acceptance criteria**
* there are many spots in OpenProject where we use `OpenProject::Configuration` instead of `Setting` where it would be perfectly valid to use the latter
* this would make life easier for some administrators including ourselves in the cloud context
* examples:
* [openproject/app/helpers/homescreen\_helper.rb at dev · opf/openproject (github.com)](https://github.com/opf/openproject/blob/dev/app/helpers/homescreen_helper.rb#L63)
* [openproject/app/helpers/omniauth\_helper.rb at dev · opf/openproject (github.com)](https://github.com/opf/openproject/blob/dev/app/helpers/omniauth_helper.rb#L45)
* [openproject/app/controllers/concerns/accounts/user\_password\_change.rb at dev · opf/openproject (github.com)](https://github.com/opf/openproject/blob/dev/app/controllers/concerns/accounts/user_password_change.rb#L37)
* I don't see a reason why you shouldn't be able to change these and many other options at runtime (even if we don't have a UI for it yet)
* if you want to pin them you can still set the via the environment as usual
**I want to** be able to change certain configurations at runtime
**so that** I can update them without requiring a restart.
**Acceptance criteria**
* there are many spots in OpenProject where we use `OpenProject::Configuration` instead of `Setting` where it would be perfectly valid to use the latter
*