clusterflux-public/docs/self-hosting.md
Clusterflux release 18cba9c609 Public release release-6756e5208c8b
Source commit: 6756e5208c8b79e83d55610251430bc1baef53a3

Public tree identity: sha256:2f58837c3759b4f466cbc274571ee71bc0d24c7552dc009c186394e99123da87
2026-07-17 04:13:46 +02:00

38 lines
1.5 KiB
Markdown

# Self-hosting
Run the public coordinator and node runtime without the hosted website.
## Start a strict local coordinator
Supply one scoped bootstrap session through protected service configuration:
~~~bash
CLUSTERFLUX_SELF_HOSTED_SESSION_SECRET="$SELF_HOSTED_SESSION_SECRET" CLUSTERFLUX_SELF_HOSTED_TENANT=my-team CLUSTERFLUX_SELF_HOSTED_PROJECT=my-project CLUSTERFLUX_SELF_HOSTED_USER=me clusterflux-coordinator --listen 127.0.0.1:7999
~~~
Connect the CLI without placing the secret in a process argument:
~~~bash
printf '%s\n' "$SELF_HOSTED_SESSION_SECRET" | clusterflux auth connect-self-hosted --coordinator 127.0.0.1:7999 --tenant my-team --project-id my-project --user me --session-secret-stdin
~~~
The CLI verifies the scope before writing ".clusterflux/session.json". On Unix,
the session file uses mode "0600".
## Attach nodes
Use the same enrollment and worker flow described in [Nodes](nodes.md), with
"--coordinator 127.0.0.1:7999".
## Network boundary
The native coordinator transport is plaintext and refuses non-loopback
listeners. For another machine, keep the coordinator on loopback and use an
authenticated SSH tunnel or deploy a trusted TLS reverse proxy that enforces the
same client boundary. Do not expose the native port directly.
## Administration
Project, node, process, task, log, artifact, debug, quota, and self-hosted admin
operations remain available through the public CLI/API. Authentik is one hosted
identity deployment, not a requirement for your coordinator.