Ecosystem & Upstream
Awesome-Sunshine catalog, upstream changelog feed, and SolarFlare vs upstream history.
SolarFlare vs upstream history#
Note
When triaging a bug, check whether it reproduces on upstream Sunshine. Fork-specific issues (Web UI, solarflare_t keys, pacing) belong to SolarFlare.
| Document | Contents |
|---|---|
| Upstream feed (below) | LizardByte/Sunshine releases: capture, encode, protocol, cross-platform hosts |
| Changelog (/docs/changelog) | Fork-only features, Linux tuning, Web UI, API scopes |
| Maintainer handbook (/docs/maintainers) | How SolarFlare versions and tags are cut |
Upstream Sunshine ecosystem#
SolarFlare stays compatible with Moonlight and much of the Sunshine ecosystem. The independent LizardByte/awesome-sunshine catalog is not maintained or endorsed by SolarFlare and may assume upstream packages, Docker images, or UI behavior. Install SolarFlare via the Quickstart; use fork tunables from Configuration; get clients at moonlight-stream.org. Test community tools (companion apps, scripts, themes) targeting the Moonlight protocol before production use.
Live feeds#
Upstream changelog: https://raw.githubusercontent.com/LizardByte/Sunshine/changelog/CHANGELOG.md. Ecosystem catalog: https://raw.githubusercontent.com/LizardByte/awesome-sunshine/master/README.md. Both render live on the Doxygen site; the website docs tab curates the SolarFlare-relevant subset above.
Links and bug triage#
Clients: Moonlight. Ecosystem catalog: awesome-sunshine. Upstream releases: LizardByte/Sunshine. Orchestrated stacks: Games on Whales. Triage rule: reproduces on stock Sunshine without fork keys, Web UI, or pacing involved — report to LizardByte and link it. Fork-specific (tunables, Web UI, API scopes, pacing) — report to vindeckyy/Solar-Flare. Never open fork PRs or issues in the LizardByte organization.