Is your feature request related to a problem? Please describe.
When updating paperpi, sometimes the configuration file changes. It's a huge hassle to update the config file because of all the user content. Updates either have to be done manually, or through some complex filtering of the config.
Describe the solution you'd like
Separate PaperPi core config from plugin config.
Describe alternatives you've considered
Keep all of the major configuration features from the [main] section into paperpi.ini and move all of the plugin configuration into paperpi_plugins.ini. This would apply to the config files in /etc/ and ~/.config.
The installer could easily check the paperpi.ini for version compatibility and and alert the user of potential issues or try to migrate in new changes (e.g. new config variables) in place.
Is your feature request related to a problem? Please describe. When updating paperpi, sometimes the configuration file changes. It's a huge hassle to update the config file because of all the user content. Updates either have to be done manually, or through some complex filtering of the config.
Describe the solution you'd like Separate PaperPi core config from plugin config.
Describe alternatives you've considered Keep all of the major configuration features from the
[main]
section intopaperpi.ini
and move all of the plugin configuration intopaperpi_plugins.ini
. This would apply to the config files in /etc/ and ~/.config.The installer could easily check the
paperpi.ini
for version compatibility and and alert the user of potential issues or try to migrate in new changes (e.g. new config variables) in place.