forked from NYANDEV/forgejo
35f37a3625
One of the repeatedly reported issues has been that gitea produces too much console logging during set up even if the console logger is turned off. Fundamentally this is due to some otherwise very helpful logging that has to occur before logging is set up. This has come to a head with the merging of #16243 where otherwise potentially helpful Trace logging in the git module now appears on the console. This PR proposes three things: 1. Change the initial default logger to Info not Trace. 2. Change the logging for the AppPath things to Info in recompense. 3. Add two new command line options to gitea web: --quiet and --verbose `gitea web -q` or `gitea web --quiet` will only log Fatal level initially. `gitea web -verbose` will log at Trace. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io> |
||
|---|---|---|
| .. | ||
| admin.go | ||
| admin_auth_ldap.go | ||
| admin_auth_ldap_test.go | ||
| cert.go | ||
| cmd.go | ||
| convert.go | ||
| docs.go | ||
| doctor.go | ||
| dump.go | ||
| dump_repo.go | ||
| embedded.go | ||
| embedded_stub.go | ||
| generate.go | ||
| hook.go | ||
| keys.go | ||
| mailer.go | ||
| manager.go | ||
| migrate.go | ||
| migrate_storage.go | ||
| restore_repo.go | ||
| serv.go | ||
| web.go | ||
| web_graceful.go | ||
| web_letsencrypt.go | ||