Deployment overview
Rediflow: Project flow. Portfolio flow. One flow.
Rediflow runs on Podman or Docker — the same stack most organisations already use. No new infrastructure. This page helps you choose the right path.
Podman and Docker — both supported
Rediflow works with both Podman and Docker. Use podman compose or docker compose — the compose files are standard OCI format and work with either runtime.
| Aspect | Podman | Docker |
|---|---|---|
| Build | podman compose build |
make DOCKER=1 build or docker compose build |
| Run | podman compose up -d |
make DOCKER=1 up or docker compose up -d |
| Registry image | podman pull registry.gitlab.com/... |
docker pull registry.gitlab.com/... |
Two deployment paths
| Path | When to use | Where to go |
|---|---|---|
| Build locally | You have the source tree and want to build the image yourself (dev, custom builds) | Run with Podman or Docker |
| Pre-built image | You want to deploy QA or production without building (recommended for most deployments) | Deploy QA and production |
Prerequisites
- PostgreSQL 18+ — Always containerised; the app will not start with SQLite.
- Container runtime — Podman or Docker with Compose.
- Configuration —
DATABASE_URL,SECRET_KEY, and optional OIDC (OpenID Connect) variables. See Configuration.
Deployment guides
| Document | Description |
|---|---|
| Run with Podman or Docker | Build image locally, run with compose (dev or QA) |
| Deploy QA and production | Use pre-built image from registry; no local build |
| Deploy on containerized Ubuntu | Nested containers (LXD/LXC): DB and app on same host |
| Deploy on containerized Rocky Linux | Same for Rocky Linux 10.1 |
| Containers survive host reboot | Auto-start db and app after reboot |
See also
- Requirements — System requirements, database, OIDC
- Configuration — Environment variables, .env files
- QA verification — Verify deployment is healthy before handover
← Home · Run with Podman or Docker · Deploy QA and production · Requirements