Allen Wild 2186a99c76 cmd/serv: actually exit after fatal errors (#7458) ... Regression in 356854fc5f, where a log.Fatal call was removed. log.Fatal calls os.Exit(1) as intended, but without it the fail() function returns normally and execution continues past the fatal error, causing a panic. This is visible as a go panic log and stack trace returned to the SSH client, which is not only ugly, it leaks server and build system information. Fix by removing the stray return statement so that the fail() function always calls os.Exit(1). Fixes: https://github.com/go-gitea/gitea/issues/7457 Signed-off-by: Allen Wild <allenwild93@gmail.com>		2019-07-13 21:38:18 +01:00
..
admin_auth_ldap_test.go	Add CLI commands to manage LDAP authentication source (#6681)	2019-06-17 14:32:20 -04:00
admin_auth_ldap.go	Add CLI commands to manage LDAP authentication source (#6681)	2019-06-17 14:32:20 -04:00
admin.go	Add CLI commands to manage LDAP authentication source (#6681)	2019-06-17 14:32:20 -04:00
cert.go
cmd.go
convert.go
dump.go
generate.go
hook.go	#6946 Run hooks on merge/edit and cope with protected branches (#6961)	2019-07-01 09:18:13 +08:00
keys.go
migrate.go
serv.go	cmd/serv: actually exit after fatal errors (#7458)	2019-07-13 21:38:18 +01:00
web_graceful.go
web_windows.go
web.go	Use certmanager provided TLSConfig for LetsEncrypt (#7229)	2019-06-17 13:33:55 -04:00