Sanitized single-commit public mirror of recipe-maintainer. - Removed test-ssh/.testenv (live creds); added test-ssh/.testenv.example placeholders. - Removed plans/ and planned-updates/ (deployment-planning docs) so no client/ deployment domains appear in the public repo. - All other secret stores were already gitignored. - docs.coopcloud.tech retained as a submodule (public upstream).
1.6 KiB
1.6 KiB
La Suite Meet — First-Time Setup
Prerequisites
- DNS:
lasuite-meet.<domain_suffix>must resolve to the server - DNS:
livekit-meet.<domain_suffix>must resolve to the server (LiveKit signaling) - Keycloak must be deployed and running (dependency)
- Firewall must allow TCP 7881, UDP 7882 (WebRTC), and UDP 443 (TURN relay)
Steps
-
Create the app:
abra app new lasuite-meet --server <SERVER> --domain lasuite-meet.<DOMAIN_SUFFIX> --no-input -
Generate secrets:
abra app secret generate lasuite-meet.<DOMAIN_SUFFIX> --all -m --no-inputSave output to
recipe-info/testsecrets/lasuite-meet.<DOMAIN_SUFFIX>. -
Deploy:
abra app deploy lasuite-meet.<DOMAIN_SUFFIX> --chaos --force --no-input -
Keycloak SSO integration:
python3 recipe-info/lasuite-meet/setup_keycloak_integration.pyThis creates a
lasuite-meetrealm, OIDC client, and two test users in Keycloak. It also inserts the client secret and updates the env file. -
Redeploy with SSO config:
abra app deploy lasuite-meet.<DOMAIN_SUFFIX> --chaos --force --no-input -
Verify: curl
https://lasuite-meet.<DOMAIN_SUFFIX>returns HTTP 200.
Notes
- lasuite-meet has no published versions yet — must use
--chaosfor all commands. - Credentials are saved to
recipe-info/lasuite-meet/keycloak-test-credentials.<DOMAIN_SUFFIX>.toml. - OIDC test users:
testuser/testpass123andtestuser2/testpass123. - TURN relay requires the server to have a direct public IP (not behind NAT). See test.md for details.