[Feature] Allow settings that are not defined in the config file to be editable in the GUI

[ImranR98]

I have searched the existing feature requests to make sure this is not a duplicate request.

• Yes

The feature

Currently, the settings UI and config file are mutually exclusive ways to configure Immich - if you have a config file, all UI settings are disabled.

It would be useful if we could apply certain settings through the config file (the UI for those settings would be disabled), but anything missing/undefined in the config file would still be adjustable in the UI.

My use case for this is for a public-facing instance protected by OAuth. Configuring OAuth and disabling email/password login via a config file is much more secure than doing so via the UI. Because in the latter case, there is a short window of time between the app startup and first-time admin setup (during that time anyone could create an admin account since it's an internet-facing instance). It would be good to keep that the config file for auth settings, while leaving everything else for experimentation which is easier through the UI. I'm sure there are other situations where this feature may be useful.

Platform

• Server
• Web
• Mobile

[bo0tzz]

We considered this before but decided against it as working out which config source to give priority to, and clearly surfacing to the user which config is coming from where, gets pretty tricky.