Skip to content

Dropnook 2.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Oct 19:01
Immutable release. Only release title and notes can be modified.
v2.2.0
3f1d072
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Dropnook 2.2.0 — certificates straight from Cert Warden.

  • Cert Warden: with CERTWARDEN_ENDPOINT_URL and CERT_INT_NAME, CERT_INT_CERT_API, CERT_INT_KEY_API in the .env, drop fetches its certificate itself — no folder of certificates needed. It checks that key and certificate belong together before using them, and fetches a new one CERT_CHECK_DAY days (preset 30) before the current one expires; the log says what was fetched, never the keys.
  • HTTPS for drop-share too: with CERT_PUB_… — or, without, when drop's certificate is a wildcard that covers drop-share — drop hands drop-share its certificate, and drop-share serves HTTPS on port 443 as well. A wildcard is fetched only once. Only drop talks to Cert Warden; port 80 keeps working for your reverse proxy.
  • The .env template is tidier: one short comment per setting. Your own .env keeps working as it is.

Nothing to change on your side: Check for Updates → Update. To use Cert Warden, add its settings to the .env (template: compose-projects-drop/.env.example) and take the current compose.yaml; Community Apps: the new fields are under Show more settings.

What's Changed

  • 2.2.0: certificates from Cert Warden, HTTPS for drop-share by @dropnook in #9

Full Changelog: v2.1.0...v2.2.0

Contributors

dropnook
Assets 3
Loading