Zum Inhalt springen
Produkte

// Deployment

Container images

Fleeger ships as a set of container images — one per backend service plus the admin UI — built and pushed by CI.

Images

Image From Runs
<registry>/auth-svc Dockerfile.service service start
<registry>/inventory-svc Dockerfile.service service start
<registry>/gateway-svc Dockerfile.service service start
<registry>/ingestion-svc Dockerfile.service service start
<registry>/alerting-svc Dockerfile.service service start
<registry>/control-svc Dockerfile.service service start
<registry>/spoke-agent Dockerfile.service service --config /etc/fleeger/spoke-agent.toml
<registry>/frontend Dockerfile.frontend nginx (static SPA)
<registry>/backup Dockerfile.backup backup.sh (restore.sh ships alongside)

Dockerfile.service is one generic multi-stage build parameterised by build-args: SERVICE (the crate to compile), SERVICE_CMD (the default run args — start for the hub services, --config … for the agent, which has no start subcommand). The per-service values are kept identical in deploy/compose/compose.yaml, deploy/build-and-push.sh and .gitlab-ci.yml. A third, CACHE_ID, names the build cache per checkout (below). Each image runs its binary as PID 1 with clean signal handling; any docker run … <args> are appended.

Configuration

Backend services read /etc/fleeger/<service>.toml (or env overrides) at runtime — mount your config there. The agent reads the path given to --config.

Frontend

The frontend image is a static nginx serving the SPA with an index.html fallback. It intentionally does not proxy /api itself — route /api/* to gateway-svc at your ingress / reverse-proxy (Kubernetes Ingress, Traefik, a compose nginx, etc.). This keeps the image independent of where the gateway lives. See deploy/frontend/nginx.conf.

// Zusammenarbeit

Bereit, Ihre digitale Infrastruktur zu bauen?

Ob individuelle Automatisierung für Ihr Unternehmen oder ein durchgeplantes Netzwerk für Ihr Zuhause — lassen Sie uns über das Projekt sprechen.