grim/hgkeeper

Replace logrus with zap logging

13 months ago, aklitzing
4a8207ba4501
Replace logrus with zap logging

logrus is in maintenance-mode and links to zap and others by itself.
zap has some really good benchmarks and default log output looks a little bit cleaner.

So let's move to zap logging.

Reviewed at https://reviews.imfreedom.org/r/2413/
# HGKeeper
[ ![Issues](https://img.shields.io/badge/Issues-YouTrack-ee3b8b.svg) ](https://issues.imfreedom.org/issues/HGKEEPER?u=1)
HGKeeper is an server for [mercurial](https://www.mercurial-scm.org/)
repositories. It provides access control for SSH access and public HTTP
access via hgweb.
It was originally designed to be run in a container but recently support has
been added to run it from an existing openssh-server.
## Documentation
You can find the full documentation
[here](https://docs.imfreedom.org/hgkeeper/).
## License
HGKeeper is licensed under the GNU AFFERO GENERAL PUBLIC LICENSE version 3.
## Status
This project has been used for awhile in production environment, but every
environment is different. So, if you find issues, or are looking for ways to
help, please check out our
[issue tracker](https://issues.imfreedom.org/issues/HGKEEPER?u=1).
## Building
You can build hgkeeper with the following command:
```
$ go build
```
## Downloads
You can find downloads
[here](https://sourceforge.net/projects/pidgin/files/HGKeeper/).
Binaries are signed with grim's 40DE 1DC7 288F E3F5 0AB9 38C5 48F6 6AFF D9BD
B729 PGP key which can be found on [keybase.io/grim](https://keybase.io/grim).