Settings UI is locked

[nebulon]

Interesting, so we moved to a preconfigured .json config for OpenID now, I didn't realize the whole settings UI then gets locked...have to see how to lift that restriction

[nebulon]

So the latest package version now allows to change the config file. Most of the settings UI is disabled as the config file is the single source of truth for settings now: https://docs.cloudron.io/apps/immich/#settings

[luckow]

@nebulon

The app no longer starts after the last update. Missing immich.json

[nebulon]

And the app starts if you place a file at /app/data/immich.json with {} as content? Or is this maybe some other failure? Anything in the logs about this?

[luckow]

Let's see, in a few minutes. Restore a backup.

[girish]

@luckow Which package version are you on? I am thinking you are maybe a version behind the latest version.

[luckow]

@girish I'm now restoring to v1.60.2.

[nebulon]

The version between should have started fine though as well, just the settings UI would not be enabled.

[taisau]

The Cloudron docs say that the settings are coming from /app/data/immich.json; however, the file only contains {}. Where are the OAuth settings coming from? I don't want to copy the Immich defaults into the settings file, which presumably would break OAuth.
...
I was able to export the settings .json from the UI, and paste them into /app/data/immich.json, and then edit there.

[nebulon]

The OAuth and all package specific settings will be merge into the /app/data/immich.json on runtime. If they were set manually, they will be overwritten. You can see those jq lines at https://git.cloudron.io/cloudron/immich-app/-/blob/main/start.sh?ref_type=heads#L21

[rollermy]

Hey,
I had a storage template set up and noticed today it hasn't been running since may. And other of my settings were changed.
I found that the UI is locked and set to default? settings.
I go to the file and just find {}

Can we please enable changing the settings in the UI again?

[nebulon]

I guess we first have to find a way to pre-setup necessary config variables programmatically and ideally lock only those in the UI. Currently most of the settings UI is locked once a config file exists.

Maybe you could create a feature request upstream to only lock settings in the UI which are set in the config file.