Changelog History
-
v1.10.2 Changes
July 20, 2019#193 Permit specifying an
ssh_socket_heartbeat
for the SSH mechanism. This can alleviate stalled deploys in widely-threaded execution. -
v1.10.1 Changes
December 06, 2018๐ #190 Lower logging level to
DEBUG
for container inspect output during deploy. This prevents printing env vars in deployment logs, as those vars often contain secrets. -
v1.10.0 Changes
October 12, 2018๐ New in this release:
- #189: Allow setting the
pid
namespacing mode on containers.
- #189: Allow setting the
-
v1.9.2 Changes
July 27, 2018๐ New in this release:
๐ #188 Environment variables may be sourced from lambdas, which are evaluated during deploy time. This permits calling functions to specify different environment variables per host.
-
v1.9.1 Changes
April 16, 2018๐ SSH support is considered stable, as it has performed well for several months.
๐ One new fix in this release: #187 adds the
unless-stopped
restart policy. -
v1.9.0-beta Changes
October 26, 2017๐ This release adds beta SSH support for teams deploying to Docker hosts which do not expose their TCP sockets over the network.
-
v1.8.10 Changes
February 04, 2017Two fixs and one feature, for a balanced diet.
๐ Fixed: #164 via #177 - containers in host networking mode may now define a public port to be used during healthchecks. The port mapping will be passed through to Docker, but it should be ignored by the server.
๐ Fixed: #128 via #147 - manually set container names were not obeyed, now they are. If you have a
name:
set in your deploy tasks, please read the notes on #147 to avoid having duplicate containers present after a deploy, especially in host networking mode. You should comment out thename:
directive until you're ready to manually intervene as containers may not be found during a stop operation.๐ Feature: #170 Container label support! You may now specify labels to be assigned to the containers Centurion creates. See the README for details.
-
v1.8.9 Changes
January 13, 2017๐ This fixes a bad behavior in 1.8.8 where setting a custom
stop_timeout
caused Centurion to give up too soon waiting on the response from Docker. This would result in Excon timeouts during deploys.๐ณ The response timeout is now always 120 seconds longer than the Docker stop timeout.
-
v1.8.8 Changes
December 19, 2016๐ Fixed in this release:
- ๐ณ Custom stop_timeout settings could not exceed 120 seconds due to underlying Excon default. Note that docker would still have waited for the given time before killing the container, but Centurion would give up before that time had passed. Now Docker and Centurion should agree on how long to wait for containers to stop.
- ๐ Documentation corrections.