[x] Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
[x] Submit one item per pull request. This eases reviewing and speeds up inclusion.
[x] Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
[x] Additions are inserted preserving alphabetical order.
[x] The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
[x] You have searched the repository for any relevant issues or PRs, including closed ones.
[x] Any category you are creating has the minimum requirement of 3 items.
[x] Any software project you are adding to the list is actively maintained.
[x] The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.
Please take some time to answer the following questions as best you can:
Why is it awesome?
It's totally free and free forever, unlike Varnish that has an enterprise plan. It supports more RFCs than Varnish.
Have you used it? For how long?
I maintain it.
Is this in a personal or professional setup?
It's used in production by many companies.
How many devices/users/services/... do you manage with it?
More than 100k users.
Biggest pros/cons compared to other solutions?
Because it's written in go it's less efficient than Varnish. But it has more features.
Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
Thank you for taking the time to work on a PR for Awesome-Sysadmin!
To ensure your PR is dealt with swiftly please check the following:
DemoandClientsare optional. Do not add a duplicateSource codelink if it is the same as the main link. Keep the short description under 80 characters and use sentence case for it, even if the project's webpage or readme uses another capitalisation.Demolinks should only be used for interactive demos, i.e. not video demonstrations.- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`Languagetag is the main server-side requirement for the software. Don't include frameworks or specific dialects.Please take some time to answer the following questions as best you can:
It's totally free and free forever, unlike Varnish that has an enterprise plan. It supports more RFCs than Varnish.
I maintain it.
It's used in production by many companies.
More than 100k users.
Because it's written in go it's less efficient than Varnish. But it has more features.