Releases: sensiblecodeio/hanoverd
v0.14.0: Upgrade to Go 1.12.10
This release updates the build to Go 1.12.10.
v0.13.0: Upgrade to Go 1.12.1 and use Go modules
- #107 Upgrade to Go 1.12.1 and use Go modules
v0.12.0: Add `--mount` option; delete intermediate build containers
v0.11.0: Update dependencies
v0.10.1: Fix for pushing images from the builder
- This update includes #100 which fixes a "Bad parameters and missing X-Registry-Auth" while pushing images from the builder.
v0.10.0: Update to use official docker go API
This release contains two bug fixes.
One is that docker had deprecated part of the API, and the other is that it got more strict about hostnames. Previously, hanoverd was using underscore in hostnames which happened to work in the past but was invalid.
PR #97 updates imports for the ScraperWiki -> SensibleCode rename
PR #98 fixes the underscore in hostname bug.
PR #99 is a major update to use the official Docker Go API and might break things. Please beware.
v0.9: Inject internal environment variables
This release contains one change:
- #94 Inject internal environment variables
Executables inside the a container run by Hanoverd can now make use of the following environment variables:
HANOVERD_IMAGE
HANOVERD_IMAGE_REPO
HANOVERD_IMAGE_TAGDIGEST
v0.9-alpha: Inject internal environment variables
This release contains two changes:
- #94 Inject internal environment variables
v0.8.0: Improved support for multiple listeners
This release contains two changes:
- #87 - Update to go1.6
- #88 - Change method for detecting process ready
- #90 - Refactor iptables code, improve iptables rules
(#88) is a bug fix and feature improvement. It makes deploys more reliable in case there are multiple listeners.
The old behaviour was that hanoverd took one port and made requests to --status-uri
until it saw a 200 OK. The problem was if you introduced a port which would not return 200 OK, it would not start.
In this release, hanoverd poll all listeners simultaneously until one succeeds, or all have failed, or timeout.
#90 makes improvements to the iptables rules. It now means that traffic coming to the container from off-machine has the correct remote IP address visible from within the container.
(Note: this tag was forcibly updated 1 day after release)
v0.8.0-pre: Experimental pre-release
Add comment to iptables rules