⚠️ Please verify that this feature request has NOT been suggested before.
[X] I checked and didn't find similar feature request
🏷️ Feature Request Type
Other
🔖 Feature description
Save settings, dashboards, and monitors config, in a different place other than a single .DB file.
So we can include those files on Git and have historical data and visual diffs of what was changed individually per section.
✔️ Solution
It would be great to have settings stored under /app/data/settings/ as JSON or YAML.
❓ Alternatives
I'm currently adding kuma.db to Git, but it keeps changing every 1 minute or so, and it is most likely including data that is not crucial to restore an instance in case of an issue.
📝 Additional Context
It could help with the UI backups as well, as we could just zip the /settings folder and restore and override everything inside of it.
Or instead of replacing, we could "merge" existing settings with the ones being imported.
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
Save settings, dashboards, and monitors config, in a different place other than a single
.DB
file. So we can include those files on Git and have historical data and visual diffs of what was changed individually per section.✔️ Solution
It would be great to have settings stored under
/app/data/settings/
asJSON
orYAML
.❓ Alternatives
I'm currently adding
kuma.db
to Git, but it keeps changing every 1 minute or so, and it is most likely including data that is not crucial to restore an instance in case of an issue.📝 Additional Context
It could help with the UI backups as well, as we could just zip the
/settings
folder and restore and override everything inside of it. Or instead of replacing, we could "merge" existing settings with the ones being imported.