The ConfigsManager Sync feature allows you to quickly save and restore all your configuration files in the cloud.
1.Set up a keying vault: Tool tries to check keyring backends in this oreder:
If you are getting errors like
file doesn't existwhen tool tries to accesspasstry initializingpass init [gpg-id/email]couple of times
Log into Dropbox:
cm sync auth --dropbox
You will receive a link from the tool. Follow the OAuth2 workflow by opening the link and entering the code provided.
Push all your configuration files and metadata to the cloud:
cm sync push
Stores not only the files but also their paths and metadata at the moment of the push.
Pull configs from the cloud with different options:
1. Pull to the current folder:
cm sync pull [config_key_in_cloud]
2. Pull to a specific folder:
cm sync pull [config_key_in_cloud] [path/]
The tool creates folders automatically if they do not exist.
3. Pull to the original path (--sp flag):
cm sync pull [config_key_in_cloud] --sp
--spstands for Determined Path – the original path where the config was located when pushed. Example: Fish shell config is stored in~/.config/fish/config.fish. When pulling with--sp, the tool restores it to the correct location automatically.
4. Pull all configs to their determined paths (killer feature!):
cm sync pull --all --sp
Automatically restores all synced configs to the proper folders.
The logout command removes saved authentication tokens from your system.
Usage: Logout from all cloud services
cm sync logout
Logout only from Dropbox
cm sync logout --dropbox
The command safely deletes access and refresh tokens stored by ConfigsManager.