Skip to content

environment-to-ini tracking bug #27541

Closed
@n9

Description

@n9

Description

There are known issues with environment-to-ini: https://gitea.com/gitea/helm-chart/issues/356

However, I have not found an issue this repo, where the implementation of environment-to-ini is located.

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Currently, the issue only occurs when environment-to-ini is explicitly used.

However, @silverwind mentioned in #24804 (comment) that there is an intention to merge enviornment-to-ini into the codebase. (I am not sure, whether this may cause then also issues in other deployments.)

Database

None

Further notes

In my case, the issue occurs during the configuration of "custom logger modes":

Failed to load writer mode "router" for logger router: invalid log writer type (mode): router, maybe it needs something like 'MODE=file' in [log.router] section
Failed to load writer mode "xorm" for logger xorm: invalid log writer type (mode): xorm, maybe it needs something like 'MODE=file' in [log.xorm] section

This is because environment-to-ini is unable to write [log.router] MODE=console to app.ini, as it is a default value.

(In this case, however, I am not sure what should be fixed, whether the environment-to-ini or "custom logger modes".)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions