zeripath 1bf40ca0df Gitea serv, hooks, manager and the like should always display Fatals (#13032) ... The gitea cmd/serv.go setup function deletes the console logger to prevent stdout interference with commands. However, the problem is that it then calls setting.NewContext which may cause an exit with log.Fatal - which will then not be shown. Now, log.Fatal is so disastrous that the interference that logging causes is wanted. However, we can avoid stdout interference by emitting on stderr. This PR forces the creation of a console logger on stderr listening on Fatal for these commands. Most commands have a `--debug` option now that will print more reasons too - however, defaulting to give the log for Fatal seems reasonable. Signed-off-by: Andrew Thornton <art27@cantab.net>		2020-10-07 16:44:16 -04:00
..
admin_auth_ldap_test.go
admin_auth_ldap.go
admin.go	Check passwords against HaveIBeenPwned (#12716)	2020-09-08 17:06:39 -05:00
cert.go
cmd.go
convert.go
doctor.go	Add command to recreate tables (#12407)	2020-09-06 22:52:01 +01:00
dump.go	Add default storage configurations (#12813)	2020-09-29 12:05:13 +03:00
embedded_stub.go
embedded.go
generate.go
hook.go	Rename models.ProtectedBranchRepoID to models.EnvRepoID and ensure EnvPusherEmail is set (#12646)	2020-08-30 08:24:39 +01:00
keys.go
manager.go	Pause, Resume, Release&Reopen, Add and Remove Logging from command line (#11777)	2020-07-05 20:07:07 -04:00
migrate_storage.go	Add default storage configurations (#12813)	2020-09-29 12:05:13 +03:00
migrate.go
serv.go	Gitea serv, hooks, manager and the like should always display Fatals (#13032)	2020-10-07 16:44:16 -04:00
web_graceful.go
web.go	Refactor use TrimSuffix instead of TrimRight (#12993)	2020-10-01 06:54:34 +01:00