Closed alex-ibb closed 1 year ago
Thank you, @CypherpunkSamurai .
It seems it will be changed to 'console' after the initilization, regardless the value in the docker-compose file.
To change it, one need to edit the app.ini
after the initilization.
Wondering the considerations to force
the values of MODE
and ROUTER
to console
in the install.go
.
Seems confusing.
The change comes from d65cd5677af3df5d616bf48dfd4be354e23c184f, before that commit, it's file
.
Copy, thank you @lunny
@zeripath Hi~ For the commit, to change the default values of MODE and ROUTER, what are the considerations to hard-code them to "console"?
No particular reason.
-> Do not overwrite the log mode when installing #25203
Description
Docker image: gitea/gitea:1.19.3 Platform: x64 OS: Ubuntu 22.04.3 Server (Minimized)
Problem: the value of log__MODE changed to
console
after the initialization step.Steps to reproduce:
Draft an
docker-compose.yml
file with the followinglog
related section:docker-compose -f docker-compose.yml up -d
to start the container and open its site for initialization.Administrator Account Settings
section, usingcat <container_root>/data/gitea/conf/app.ini
to checklog
related settings, it reads:Install Gitea
button, the site would redirect to a user page, then re-check the content, it reads:The value of
MODE
changed toconsole
incorrectly. To a personal unstandering, given in thedocker-compose.yml
it'sfile
and all required values related have given, it should remind to befile
after the initialization.What have I missed ?
Gitea Version
1.19.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Using Docker images. The full content of the
docker-compose.yml
:Database
SQLite