deploy-dawarich

Deployment configuration for running Dawarich with rootless Podman on Debian.

This repository contains deployment-side files only. It does not contain Dawarich application source code.

Current status

The current tested baseline is:

• Debian 13 / trixie
• rootless Podman
• podman-compose
• user systemd service
• Dawarich reachable on 127.0.0.1:3000
• health check returns {"status":"ok"}

Version tags

• deploy-0.1.0
  • Compose-based manual startup confirmed.
• deploy-0.1.1
  • Compose-based manual startup with Redis persistence fixes.
• deploy-0.2.0
  • User systemd startup confirmed.
• deploy-0.2.1
  • Runtime smoke check script added.

Files

• compose.yaml
  • Podman Compose stack definition.
• .env.example
  • Example environment file.
• .env
  • Local secret/config file. Not tracked by git.
• scripts/check-prereq.sh
  • Checks host/user prerequisites.
• scripts/check-runtime.sh
  • Checks whether the deployed stack is running correctly.
• systemd/dawarich.service
  • User systemd service unit.

Secrets

.env is intentionally excluded from git.

It contains values such as:

• POSTGRES_PASSWORD
• DATABASE_PASSWORD
• SECRET_KEY_BASE

When migrating existing data to another host, preserve the existing .env values unless there is a clear reason to rotate them.

Basic operation

Run as a non-root deployment user.

Check prerequisites:

./scripts/check-prereq.sh

Start service:

systemctl --user start dawarich.service

Stop service:

systemctl --user stop dawarich.service

Check service status:

systemctl --user status --no-pager dawarich.service

Check runtime state:

./scripts/check-runtime.sh

Check health API manually:

curl -s http://127.0.0.1:3000/api/v1/health; echo

Access

The application currently listens on the host loopback address only:

127.0.0.1:3000

For temporary access, use SSH port forwarding.

For regular access, add a reverse proxy on the host and point it to 127.0.0.1:3000.

Host-side prerequisites

Some prerequisites are outside this repository and must be configured by the host administrator, such as:

• installing required Debian packages
• creating a non-root deployment user
• configuring subordinate UID/GID ranges
• enabling linger for the deployment user
• setting vm.overcommit_memory = 1

Use scripts/check-prereq.sh to verify the current state.

Backup and migration

Backup/restore is not yet documented.

Before using this instance for real data, define and test backup/restore for:

• PostgreSQL/PostGIS data
• Dawarich storage/public volumes
• .env