gotosocial/internal/router
embr 86e8e7fd21
Log when listening (#350)
* Log when starting letsencrypt endpoint + clearer errors

Running `gotosocial server` with the default configuration will try to
bind to :80 and listen for letsencrypt challenges, which will fail if
running as non-root (w/o capabilities), or if eg. nginx hogs the port.

When that happens, this should make it more obvious what's wrong.

* Log what address/port we're listening on

Always nice not to have to guess. Also feels more consistent than just
doing it for the letsencrypt endpoint.
2021-12-20 10:34:57 +01:00
..
attach.go clean up some weirdness in the router (#80) 2021-07-07 15:46:42 +02:00
cors.go Implement Cobra CLI tooling, Viper config tooling (#336) 2021-12-07 13:31:39 +01:00
logger.go reference global logrus (#274) 2021-10-11 14:37:33 +02:00
router.go Log when listening (#350) 2021-12-20 10:34:57 +01:00
session.go Implement Cobra CLI tooling, Viper config tooling (#336) 2021-12-07 13:31:39 +01:00
session_test.go Implement Cobra CLI tooling, Viper config tooling (#336) 2021-12-07 13:31:39 +01:00
template.go Implement Cobra CLI tooling, Viper config tooling (#336) 2021-12-07 13:31:39 +01:00