Fluxer - one-click service template

[lemintare]

Service

Fluxer is an open source (AGPLv3) chat and VoIP platform, a self-hostable
Discord alternative.

• Website: https://fluxer.app
• Repo: https://github.com/fluxerapp/fluxer
• Self-hosting docs: https://docs.fluxer.app/operator/get-started
• Upstream compose: deploy/self-hosting/docker-compose.yml

Upstream ships a maintained Compose stack with published images on
ghcr.io/fluxerapp/*, so a template would track official artifacts rather
than a third-party fork.

Why a template would help

Everything is served under a single hostname with path routing (/api,
/gateway, /media, /admin, /livekit), which maps cleanly onto one
Coolify FQDN. The manual route currently requires patching the upstream
Compose file before it will run behind Coolify's proxy, which is exactly
the kind of friction a template removes.

What the template would need

Straightforward:

• The stack's own Caddy publishes 80, 443 and 443/udp, which collides
  with Coolify's proxy. Dropping the ports block, setting
  FLUXER_CADDY_SITE_ADDRESS=:80 and exposing it with
  SERVICE_FQDN_CADDY_80 works. Caddy has to stay in the stack because it
  owns the path routing; Traefik terminates TLS in front of it.
• LiveKit needs to keep its own 7881/tcp and 7882/udp published
  directly, since WebRTC media can't go through Traefik.
• ~10 secrets (Postgres, Meilisearch, S3, media proxy, admin, gateway RPC,
  LiveKit) map onto SERVICE_PASSWORD_* / SERVICE_BASE64_*.
• Caddyfile and livekit.yaml are bind mounts in the upstream Compose
  and would have to become inline content: volumes.

Known blocker:

• Web push needs a VAPID EC P-256 keypair, and both
  FLUXER_VAPID_PUBLIC_KEY and FLUXER_VAPID_PRIVATE_KEY are mandatory
  (:?) in the upstream Compose. Coolify's magic variables generate random
  strings and passwords, not keypairs, so this would need either an init
  container or an upstream change that generates them when unset.

Footprint

~20 containers (API, gateway, messages, media proxy, static proxy, admin,
app proxy, LiveKit, Postgres, Valkey, NATS, Meilisearch, SeaweedFS, plus
sharded services). Upstream states 2 vCPU / 4 GB as the minimum and
recommends 4 vCPU / 8 GB for a small active community. That is heavier than
a typical catalog entry, so it may simply be out of scope for the one-click
catalog - worth knowing either way before anyone invests time in a template.