WeaveSignal/weavesignal
Watch
2
0
Fork
You've already forked weavesignal
 0
Code Issues 17 Pull requests Projects Releases 1 Packages Wiki Activity Actions
weavesignal/deploy/cloudron/POSTINSTALL.md
The WeaveSignal contributors ad39c8c6dd The website as a landing site, the Cloudron catalogue file, MP3 on the public route 
- weavesignal.top is now a landing site (home, compare, FAQ, run your own station) with the
  documentation under /docs/; old addresses redirect; a glossary; "desk B" is "the desk".
- deploy/cloudron/CloudronVersions.json for community installs (Cloudron 10.0 or later).
- The Compose bundle's public route publishes the MP3 compatibility stream too.
- The Cloudron guide no longer names a branch; packagerUrl names the repository.
2026-11-04 15:41:17 +00:00

1.8 KiB
Raw Permalink Blame History

Your station is installed. The guide is at https://weavesignal.top/docs/how-to/install-on-cloudron/.

  • The station's settings are in /app/data/weavesignal.env, and its generated secrets (the station identifier, LiveKit's key, the control plane's admin token, the listener password, and the keys that hash chatters' and staff's email addresses) are in /app/data/secrets.env. Keep the email keys: a new one finds none of the accounts made before. Open them with the File Manager; restart the app after an edit.
  • The listener stream is at https://<listener domain>/programme.opus. It is in no directory and open to anyone with the address; set LISTENERS_AUTH=on in weavesignal.env to ask for the user listener and LISTENERS_PASSWORD from secrets.env.
  • The player page, with call-in and the live chat, is at https://<public domain>/; podcast feeds, show cards and episode files are served there too. The chat's sign-in codes are sent through Cloudron's mail (MAIL_MODE in weavesignal.env).
  • Staff: in the studio app, choose Use the station key instead with CONTROL_ADMIN_TOKEN, add yourself as an admin under Settings → Staff, then sign in as yourself. Each member of staff then gets their own account there.
  • Room tokens: POST /api/v1/room/tokens with a staff sign-in or CONTROL_ADMIN_TOKEN as the bearer.
  • The public ports (room media over UDP, TURN over TLS, and the optional TURN over UDP and ICE over TCP) must be open in the server's firewall and any cloud firewall.
  • The station's own domain is behind Cloudron's login; the listener, room and public domains are not, and are protected by the listener password, by room tokens, and by serving only the public routes.