Add RFC: Automatic Configuration Backup #31
Conversation
| location when they are written. This could be configured by the user to be a synced folder (e.g. Dropbox or Google Drive) | ||
| or a network drive, but could also be simply a different storage drive for redundancy. | ||
|
|
||
| Versioned backups could be implemented by allowing backups to be sorted by date or time in the filename or folder path. |
There was a problem hiding this comment.
If it's a single file, just naming them with a datetime convention would do the trick.
If you do go down the path of having assets (optionally?) backed up as well, then would using Git be a better choice?
Not sure how many things would need to be included for each version as I don't know much about the settings files...
|
I feel like it's not OBS's job to Backup the configs and upload them to the cloud. However, if the XDG Basedir Specification is implemented fully, that would make things a lot easier. I.e. At the moment, OBS just puts everything under $HOME/.config/obs-studio/ (whether it uses the home variable, or looks for the XDG_CONFIG_HOME env or just hardcodes the path, I don't know. My point is everything is currently being put into the config folder, where the config, data, cache and runtime folders should all be utilized for the appropriate types of data. |
Summary
Add built-in backup functionality to OBS Studio.
Motivation
As of writing OBS does not offer any native option for users to have their settings (profiles and scene collections) automatically backed up to cloud, local, or network storage. At the moment backing up OBS' entire configuration data is also not easily possible or intuitively explained for non-technical users.
This RFC is meant to firstly facilitate a discussion to determine a high-level approach to implementing a backup feature in OBS Studio, before then formulating a specification for the low-level implementation of the chosen approach.
View the RFC