You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
SQLite for configuration files like this is overkill and would make things much too complicated. All of the additional features would rarely to never be used for this kind of key-value configuration file. It's much easier to go with one of the text formats JSON/YAML already mentioned above or TOML and use them in a well-defined file/directory structure below sunshine's configuration directory root (for an example see my comment on #87 (comment)).
Especially for development it's much easier to just have to edit a text file instead of having to deal with SQL. It's also easier to restore said textfile instead of having to fix the SQLite database state in case of problems. Same assumption is likely true for unit testing.
Especially for development it's much easier to just have to edit a text file instead of having to deal with SQL. It's also easier to restore said textfile instead of having to fix the SQLite database state in case of problems. Same assumption is likely true for unit testing.
This is also true for issue debugging where the reporter can just (be asked to) attach a (possible redacted) text configuration file easily compared to an SQL based approach.
There's more than config files that need to be moved. There's a lot of features behind asked for that make no sense putting in json or toml files.
per app config
per client config
game metadata, like plex/jellyfin
revamped prep commands
And probably more I can't think of right now.
It also makes it's easier when things change because we can do a proper migration, instead of telling users delete the config directory and start over because something was missed.
Especially for development it's much easier to just have to edit a text file instead of having to deal with SQL. It's also easier to restore said textfile instead of having to fix the SQLite database state in case of problems. Same assumption is likely true for unit testing.
This is also true for issue debugging where the reporter can just (be asked to) attach a (possible redacted) text configuration file easily compared to an SQL based approach.
I haven't asked for this in a long time, we log the non standard config settings at Sunshine startup.
There's more than config files that need to be moved. There's a lot of features behind asked for that make no sense putting in json or toml files.
per app config
per client config
game metadata, like plex/jellyfin
revamped prep commands
And probably more I can't think of right now.
That's all features you can do with properly laid out and well-defined configuration files/directories. I personally see no specific need to involve the complexity of SQL for those features unless you have a need to use anything unique here that only SQL provides. It's just a different storage layout for those features depending on how you implement it and you can do that with the directory layout I've described in #87 (comment) and a unified file structure using json/yaml/toml. So I'm not really understanding why it wouldn't make sense to use a text-based format here.
It also makes it's easier when things change because we can do a proper migration, instead of telling users delete the config directory and start over because something was missed.
You'd still need an external tool to work on the DB. Text files are just much simpler and easier to access.
Just my 2c on this topic. I'm fine with it either way but IMHO SQL is just adding unnecessary complexity here and needs to be implemented with a proper table structure to make sense at all.
Activity
[-]Move Sunshine config to standard format[/-][+]Sunshine: Move config to standard format[/+]Kishi85 commentedon Oct 18, 2026
SQLite for configuration files like this is overkill and would make things much too complicated. All of the additional features would rarely to never be used for this kind of key-value configuration file. It's much easier to go with one of the text formats JSON/YAML already mentioned above or TOML and use them in a well-defined file/directory structure below sunshine's configuration directory root (for an example see my comment on #87 (comment)).
Especially for development it's much easier to just have to edit a text file instead of having to deal with SQL. It's also easier to restore said textfile instead of having to fix the SQLite database state in case of problems. Same assumption is likely true for unit testing.
Kishi85 commentedon Oct 18, 2026
This is also true for issue debugging where the reporter can just (be asked to) attach a (possible redacted) text configuration file easily compared to an SQL based approach.
ReenigneArcher commentedon Oct 18, 2026
There's more than config files that need to be moved. There's a lot of features behind asked for that make no sense putting in json or toml files.
And probably more I can't think of right now.
It also makes it's easier when things change because we can do a proper migration, instead of telling users delete the config directory and start over because something was missed.
https://sqlitebrowser.org/ makes it very easy to work with the db files.
ReenigneArcher commentedon Oct 18, 2026
I haven't asked for this in a long time, we log the non standard config settings at Sunshine startup.
Kishi85 commentedon Oct 18, 2026
That's all features you can do with properly laid out and well-defined configuration files/directories. I personally see no specific need to involve the complexity of SQL for those features unless you have a need to use anything unique here that only SQL provides. It's just a different storage layout for those features depending on how you implement it and you can do that with the directory layout I've described in #87 (comment) and a unified file structure using json/yaml/toml. So I'm not really understanding why it wouldn't make sense to use a text-based format here.
You'd still need an external tool to work on the DB. Text files are just much simpler and easier to access.
Just my 2c on this topic. I'm fine with it either way but IMHO SQL is just adding unnecessary complexity here and needs to be implemented with a proper table structure to make sense at all.