v0.1.4

Bugfixes

• Prevent initial setup from accepting configurations that fail when reloaded.
• Allow project IDs containing token without treating them as secrets.

Breaking changes

• Require schema v2 machine state: regenerate older development state before using v0.1.4.
• Require configuration files named host.yml: rename .yaml files and update loader scripts.
• Require mapping syntax for pgbouncer and http: replace boolean shorthands with enabled mappings.

v0.1.3

Breaking changes

• Replace role-qualified DNS and proxy routes with <project>.<host-id>.<base-domain>, and update matching http.domain overrides.

v0.1.2

Improvements

• Use the exact Git tag as the release version.

v0.1.1

Breaking changes

• Install evdb==0.1.1 and replace evanovation_db imports with evdb.

v0.1.0

evdb 0.1.0 is the first release of a host-local manager for self-hosted Postgres and Redis-compatible databases.

What's changed

• Install a standalone Linux binary on AMD64 or ARM64 without Python; the installer verifies the archive checksum, and guided setup configures routing and scheduled maintenance.
• Create and manage Postgres, Dragonfly, or Redis databases through guided or direct commands, with private credentials and standard TLS connection URLs. Redis-compatible databases can also expose an HTTPS API.
• Configuration changes show a plan, require confirmation, preserve stable credentials and ports, and recover the previous healthy service when activation fails.
• Durable databases receive validated Restic backups in configured remote repositories. Scheduled backup tests restore into isolated containers, while status reports service health, configuration drift, disk space, backup freshness, and test failures.
• Live restores verify the selected backup, upload a safety backup, and health-check the restored database. If the check fails, evdb automatically restores the prior data.