fix: use acme-dns sqlite backend #25

2026-08-31T17:11:44Z

autonomic-bot commented

2026-08-31 17:11:44 +00:00

What changed

Corrects the acme-dns 2.0.2 database engine identifier from legacy sqlite3 to sqlite.

Why

The initial live staging deployment revealed that the packaged 2.x binary registers the embedded driver as sqlite; sqlite3 left its API running but unable to create the restricted account.

Evidence

The upstream 2.0.2 sample configuration specifies engine = "sqlite".
NixOS configuration evaluation succeeds with the correction.
The first deployment’s fault was contained to localhost registration; no acme-dns account was created and no Gandi DNS was modified.

After merging, I will repeat the required nixos-rebuild test, health verification, and switch, then bootstrap the account.

## What changed Corrects the acme-dns 2.0.2 database engine identifier from legacy `sqlite3` to `sqlite`. ## Why The initial live staging deployment revealed that the packaged 2.x binary registers the embedded driver as `sqlite`; `sqlite3` left its API running but unable to create the restricted account. ## Evidence - The upstream 2.0.2 sample configuration specifies `engine = "sqlite"`. - NixOS configuration evaluation succeeds with the correction. - The first deployment’s fault was contained to localhost registration; no acme-dns account was created and no Gandi DNS was modified. After merging, I will repeat the required `nixos-rebuild test`, health verification, and `switch`, then bootstrap the account.

autonomic-bot added 1 commit 2026-08-31 17:11:45 +00:00

fix: use acme-dns sqlite backend f6e977c69e

autonomic-bot merged commit 1c2d5e9f7f into main

2026-08-31 17:11:52 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: recipe-maintainers/cc-ci#25