- When streaming events, also take notice of rename events. This may fix issues when using docker-compose, which sometimes creates a container with a prefixed name and then renames it immediately.
- Remove support for SSL certificate generation and deployment. I'm not aware of any deployment of Dotege actually using this functionality, and it's a non-trivial maintenance burden. If you are using this functionality, please get in touch (and stick with v1 for now!)
- Remove support for ACLs and users. This was very difficult to configure, and is an extremely niche use case. This will be replaced with a more general way to pass custom data to templates, which can then use it how they see fit.
- Added a
DOTEGE_POLLoption that makes Dotege poll the container list instead of using events. This may help to mitigate some issues caused by strange state when using docker-compose. - The
DOTEGE_DEBUGenv var is no longer used. Dotege's default logging will be slightly more verbose. - The format of Dotege's logs have changed. They are now formatted using Go's standard logger instead of a third-party logging tool.
- Update golang.org/x/net dependency to fix building on newer Go versions
- Update to Go 1.23
- Domain names in certificates and templates are now ordered consistently,
in the order they're specified in the
com.chameth.vhostlabel. Previously, these were accidentally alphabetised in a lot of situations.
- Dotege can now deploy private keys separately to their corresponding
certificates by setting
DOTEGE_CERTIFICATE_DEPLOYMENTtosplitkeys. (Thanks @Greboid)
- Update to Go 1.18
- Miscellaneous dependency updates
- Dotege can now be configured to not manage TLS certificates at all.
When
DOTEGE_CERTIFICATE_DEPLOYMENTis set todisabledno certificates will be requested or written to disk, and all certificate-related options are ignored.
- Updated the default haproxy template (thanks @Greboid):
- Updated cipher suites in line with Mozilla's current intermediate recommendations
- Don't overwrite the Strict-Transport-Security header if sent by upstream
- Remove any Server header returned from upstream
- Miscellaneous dependency updates
- You can now limit what containers Dotege will monitor by specifying the
DOTEGE_PROXYTAGenv var. Only containers with a matchingcom.chameth.proxytaglabel will then be used when generating templates. - You can now use build tags when compiling Dotege to restrict it to a single
DNS providers for ACME authentications. For example building with
-tags lego_httpreqonly includes HTTPREQ and shaves around 30MB from the resulting binary.
- Update to Go 1.17
- Miscellaneous dependency updates