internal function to export config that can be used in a trigger

[patrichard]

Is this a feature relevant to companion itself, and not a module?

• I believe this to be a feature for companion, not a module

Is there an existing issue for this?

• I have searched the existing issues

Describe the feature

It would be nice if there was an internal action to export the config. We could then set a trigger to auto export the full config on a schedule. Maybe have a field in settings that defines a file path to where the exports would go.

Usecases

This would nice to just have a consistent backup that we can restore if something goes bad, but without having to do it manually.

[istnv]

This is more important now that the config is not a simple text file.
The database should be flushed and closed when creating a backup.
Copying while Companion is active can lose recent updates if the journal is not properly synced.

This action should create the same file as the GUI Export tab, with action options for the file name and compression.
A trigger could export, then push the file to a NAS or other backup location via curl or some other app.

[Julusian]

This is more important now that the config is not a simple text file.
The database should be flushed and closed when creating a backup.
Copying while Companion is active can lose recent updates if the journal is not properly synced.

You can take the db.sqlite.bak. That is made with the sqlite backup command, and I believe is a normal sqlite file and should not have any unflushed journal. We create that with on a schedule based off the main config.

Not really a solution to this, but a workaround to getting something more reliable until this task is done