Datab
Step-by-step appliance installation

Install Guides

These are operator reference paths for institution-specific deployment candidates. Public snap and image artifacts are pending; use only an artifact supplied and verified for your institution.

Path A — snap on existing host

  1. Ubuntu 24.04 with systemd for the current image track; Ubuntu Core/snap for appliance release candidates when published.
  2. Verify the institution-specific artifact, its checksum and its release instructions before a local snap installation.
  3. sudo snap services datab-app — verify ~14 entries.
  4. sudo /snap/datab-app/current/scripts/doctor.sh — expect exit 0.
  5. Populate $SNAP_COMMON/secrets/postgres.env.
  6. Restart datab-app.flyway; the migration runs once and the backend comes up.

Path B — flash node image

  1. Choose an image published for your institution and its supported hardware architecture.
  2. Verify the SHA-256 against the value published on the Releases page.
  3. Flash to the boot disk (USB key writer + dd, or balenaEtcher).
  4. Boot the node and confirm the services named in that image's release instructions.
  5. Run doctor.sh from the console or from a SSH session.

Required configuration after install

  • DATAB_INTERNAL_API_KEY — non-blank in production. Set via snap set or environment.
  • POSTGRES_* in $SNAP_COMMON/secrets/postgres.env.
  • (Optional) GU_WAZUH_* if a Wazuh manager exists on the LAN.

Operator runbook: see Operator Docs for what to do during a healthy daily-ops day.