Problem / Motivation
I saw that a new JSON-based configuration has been introduced together with the setup assistant however some options seem to be missing. I just wanted to know how the plan is regarding the configuration. Will the env variables coexist in the future? I assume they won’t.
APP_SHORT_NAMEAPP_DESCRIPTIONPWA_ICON_URLPWA_THEME_COLORPWA_BACKGROUND_COLOREXTENSION_DIRECTORY_URLSESSION_SECRET_FILEOAUTH_CLIENT_SECRET_FILE
Especially the PWA stuff is also not in the UI yet. But no pressure if that’s still in the works.
And would you mind to have an example json config? Just like the .example.env so that package maintainers can see all the configuration options without having to keep a docker container around and manually search for them (and maybe miss one).
Thank you for this amazing project and I fully understand that things don’t change from one day to another.
Proposed Solution
Alternatives Considered
No response
Feature Area
None
Mockups / Examples
No response
Additional Context
No response
Problem / Motivation
I saw that a new JSON-based configuration has been introduced together with the setup assistant however some options seem to be missing. I just wanted to know how the plan is regarding the configuration. Will the env variables coexist in the future? I assume they won’t.
APP_SHORT_NAMEAPP_DESCRIPTIONPWA_ICON_URLPWA_THEME_COLORPWA_BACKGROUND_COLOREXTENSION_DIRECTORY_URLSESSION_SECRET_FILEOAUTH_CLIENT_SECRET_FILEEspecially the PWA stuff is also not in the UI yet. But no pressure if that’s still in the works.
And would you mind to have an example json config? Just like the
.example.envso that package maintainers can see all the configuration options without having to keep a docker container around and manually search for them (and maybe miss one).Thank you for this amazing project and I fully understand that things don’t change from one day to another.
Proposed Solution
Alternatives Considered
No response
Feature Area
None
Mockups / Examples
No response
Additional Context
No response