Community sources and acknowledgements
The documentation is checked against source code, but source code alone does not show every deployment failure or explain which detail is confusing to an operator. Community reports provide that missing evidence. This page records the people and threads that directly shaped the current documentation.
Contributors referenced in the documentation
| Contributor | Report or discussion | Documentation improved |
|---|---|---|
| arcoast | Remote YouTube login, discussion #122 | WebSocket proxy requirements and the stale-nginx diagnostic |
| arcoast | Database variable naming, discussion #123 | PostgreSQL variables as the single stack-level source of truth |
| arcoast | Authelia and Pocket ID OIDC guide, discussion #128 | Tested provider examples and callback settings |
| arcoast | Garage RPC secret, discussion #130 | Random GARAGE_RPC_SECRET generation for manual installs |
| filippobaroni | Legacy playback and stack migration, discussion #133 | Detection and migration of Compose files that still use the former image namespace |
| hugoghx | Token container environment, discussion #156 | Token service naming, internal network boundary, and current hardening limits |
| hulmgulm | First-admin setup, discussion #151 | Bootstrap status and exact-origin CORS troubleshooting |
| Toni-Vide | Unexpected sign-outs, discussion #162 | Access-token, refresh-cookie, and session troubleshooting |
| nanhoes | iOS download flow, issue #116 | Authentication propagation and artifact-path review |
| lelam183 | Imported playlist behavior, issue #135 | Import deduplication, system-playlist mapping, and background metadata repair |
| hugoghx | Livestream playback, issue #145 | Live playback and moving-window review |
| Priveetee | Live quality changes, issue #163 | Live-session and quality-switching concepts in the playback guide |
Thank you to everyone above for publishing reproducible symptoms, configuration context, and follow-up results. Their reports made the supported workflow clearer for people who will encounter the same boundary later.
How community material is used
A discussion or issue is not copied directly into the manual. Before it becomes documentation:
- The current owning repository is inspected to confirm the behavior still exists.
- The central Compose and nginx files are checked for the supported deployment.
- Sensitive values and instance-specific details are removed.
- The result is written as a reusable explanation or diagnostic.
- The original contributor and public thread are linked where the insight is used.
This matters because an older workaround can become harmful after the implementation changes. For example, the WebSocket investigation in discussion #122 remains useful, but the supported fix is to use the current bundled nginx configuration rather than copying the reporter's entire custom stack.
Issues and discussions
All user-facing reports are centralised in the TypeType repository:
- Issue tracker for bugs, features, and documentation gaps.
- Discussions for operator questions, deployment findings, ideas, and configuration examples.
When reporting a problem, include the relevant /api/version/* responses and remove tokens, cookies, passwords, internal hostnames, and private instance URLs. See Reporting issues for the full checklist.