keaz/flux-gate-ui repository overview

FluxGate Console is the web application for administering FluxGate: create and manage features, environments, teams, and rollout settings, and monitor flag usage and health.

Full documentation can be found here https://github.com/keaz/fluxgate/tree/main⁠

What is this image? • Serves the FluxGate web console as static assets over HTTP • Connects to your FluxGate Control Plane via runtime configuration (no rebuilds required) • Stateless and horizontally scalable behind a load balancer or ingress

Key capabilities • Feature and environment management • Context targeting and rollout settings • Team- and client-focused administration workflows • Real-time views powered by the Control Plane

Quick start

docker run -d \
  --name fluxgate-console \
  -p 3000:80 \
  -e BACKEND_HOST="control-plane" \
  -e BACKEND_PORT="8080" \
  -e BACKEND_PROTOCOL="http" \
  -e WS_PROTOCOL="ws" \
  keaz/flux-gate-ui :latest

# Then open http://localhost:3000

Configuration (environment variables) • BACKEND_HOST (required): Hostname or DNS name for the Control Plane API • BACKEND_PORT (required): Port for the Control Plane API (e.g., 8080) • BACKEND_PROTOCOL (required): http or https (match your ingress/LB) • WS_PROTOCOL (required): ws or wss (match your ingress/LB)

Notes • Configuration is applied at container start; no rebuild is needed when pointing the Console to another Control Plane endpoint. • Place the Console behind your standard ingress/load balancer with TLS termination for production. • The Console requires network access to the Control Plane API you operate.

Networking guidance • Publish port 80 behind a secure ingress/LB with TLS • Ensure the Console can reach your Control Plane endpoint from the runtime network • For multi-environment setups, deploy separate Console instances per environment or route by host/path