Move UI configurations that do not require restarting gitea to take effect to the admin dashboard

[hiifong]

[lunny]

It's better to split them as multiple sections.

[silverwind]

How does this work? Will it write into app.ini?

Regarding UI, I would make it so that all <input> elements are horizontally aligned.

[hiifong]

How does this work? Will it write into app.ini?

No, these configurations will be stored directly in the database in the future

Regarding UI, I would make it so that all elements are horizontally aligned.

Regarding UI issues, I will listen to your suggestions

[silverwind]

No, these configurations will be stored directly in the database in the future

And which value takes precedence when database and app.ini conflict for a setting?

[lunny]

It should be like other configurations which migrated from ini to database. Once migrated, the configuration item in the ini will be marked as deprecated and will not be read any more.

[hiifong]

No, these configurations will be stored directly in the database in the future

And which value takes precedence when database and app.ini conflict for a setting?

As @lunny said, When upgrading gitea, the configuration in ini will be migrated to the database, and the migrated configuration items will be marked as deprecated in the ini configuration. The migrated configuration items are based on the configuration in the database.

[silverwind]

It does still seem like a bit of a sketchy mechanism because config can also come from env vars (in the docker case), and you can't "mark" stuff there.

I recommend clearly mentioning this in the configuration docs, otherwise users might become confused why their env vars don't take effect.

[lunny]

DefaultTheme, Explore Paging Default Sort and Prefered Timestamp Tense should be a dropdown list.

[hiifong]

It's better to split them as multiple sections.

@lunny How about we save it for the next version?

[hiifong]

It does still seem like a bit of a sketchy mechanism because config can also come from env vars (in the docker case), and you can't "mark" stuff there.

I recommend clearly mentioning this in the configuration docs, otherwise users might become confused why their env vars don't take effect.

It seems that the ui section configuration does not support configuration from environment variables, But I'm not sure, can you tell me what configurations support getting them from environment variables?

[hiifong]

It does still seem like a bit of a sketchy mechanism because config can also come from env vars (in the docker case), and you can't "mark" stuff there.
I recommend clearly mentioning this in the configuration docs, otherwise users might become confused why their env vars don't take effect.

It seems that the ui section configuration does not support configuration from environment variables, But I'm not sure, can you tell me what configurations support getting them from environment variables?

I found the answer in docs. Excuse me.