Skip to main content
apowerb is designed to run either as a complete stack with the web interface and PostgreSQL, or as a backend service connected to your own database and infrastructure. The deployment repository ships ready-to-use assets for the most common hosting models, from local Docker setups to managed cloud services and Kubernetes.

Docker Compose

The quickest path to bring the full stack up on a single host.

Kubernetes

Prepare a cluster with kubectl and plain manifests: storage, ingress, certificates.

Helm chart

Install the application on that cluster, configure it and upgrade it.

Single VM / HTTPS

Expose the stack behind Traefik with TLS on a single VM.

​
Deployment options

Choose the operating model that fits your environment:
  • Docker Compose: best for local development, labs, and small production installs.
  • Kubernetes: prepares the cluster — storage class, ingress controller, certificate issuer — with kubectl and plain manifests.
  • Helm chart: installs and upgrades the application on that cluster; repeatable, and fits GitOps workflows.
  • Single VM / HTTPS with Traefik: useful for self-hosted environments behind a public endpoint.

​
Secrets

Secrets are not a deployment model: every option above needs the same few values, and none of them ships with one — a value committed to a public repository is not a secret.
  • Docker Compose: scripts/generate-secrets.sh writes random values for DB_PASSWORD, ENCRYPT_KEY and the service tokens into .env. It never overwrites a value that is already set: a new DB_PASSWORD would no longer match the existing database volume, and a new ENCRYPT_KEY would make every connected integration unreadable.
  • Helm chart: pass postgres.password, backend.env.encryptKey and the service tokens as values; the chart stores them in a Kubernetes Secret and refuses to install without the mandatory ones.
Keep .env and your values files out of source control, and back up ENCRYPT_KEY with them.

​
Managed and hosted platforms

The repository also includes references for common managed environments and platform-specific setups:

​
Repository assets

The deployment assets are concentrated in apowerb-hosting, which assembles the API, the web interface, and the database into a consistent stack. The same repository publishes deployment configurations and scripts for the supported environment types, making it easier to move from development to production without rewriting the stack.