Gately v0.5.6.4 released

October 23, 2026

This is a feature update in the v0.5.6 series, based on the suggestion in issue #13, improving how certificates reach other services.

Download v0.5.6.4 · GitHub Release

Copy to several local directories

A certificate's "Auto deploy" gains "Copy to local directory". Add as many directories as you need, each with its own "Run after copying" command, for example one for nginx running nginx -s reload and another for ocserv running systemctl reload ocserv. After the certificate is issued, renewed or updated it is copied and the commands run automatically; failures are retried hourly and send a "Certificate: deployment failed" notification. If the certificate files in a directory are deleted or changed, the next check copies them again.

Custom certificate file names

Both "Copy to local directory" and "Upload to SSH host" accept file names for the certificate (full chain) and the private key, such as fullchain.pem and privkey.pem. With both set, only those two files are written, so no renaming in the command is needed. Left empty, the usual <remark>.crt, .pem and .key are used. $certFile and $keyFile in the command point to the files actually written.

Upgrade notes

• The existing "Certificate mapping" is unchanged and keeps working; add directories under "Auto deploy" when you need more than one.
• Existing SSH and Docker deployment targets are not redeployed after upgrading.
• When Gately runs in Docker, local directories and commands are inside the container, so mount the target directories into it.