LizardByte / LizardByte/roadmap
Sunshine: Move config to standard format
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 25m
- Merged PRs (30d)
- 5
Description
Is there an existing issue for this item?
- I have searched the existing issues
Repositories
LizardByte/Sunshine
Languages/Skills/Technologies
C++
Description
The Sunshine config should be migrated to a standard format like JSON or YAML (or even SQLite) and then the complexities of parsing the custom format can be dropped.
We should consider a migration feature for those on the old format, but eventually should drop support for the old format altogether.
If the SQLite option is chosen, we could actually store much more information in the db such as:
- state info
- paired devices
- certs
- apps
Estimated Effort
effort:Large
Priority
priority:High
Target Milestone
6+ months
Dependencies
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the proposed JSON, YAML, and SQLite approaches against Sunshine's configuration needs, including migration from the old format. Define the chosen standard, the migration path, and which old-format support can eventually be removed; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100