git-crypt-backup

You can automate encrypted backups to private GitHub repositories by using git-crypt to encrypt workspace and configuration files. The process applies repository-specific encryption keys to protect sensitive data during daily automated or manual workflows.

Git-crypt secures sensitive files by applying repository-specific encryption keys to transparently encrypt and decrypt workspace data within private GitHub repositories. Only users who possess the exported keys can unlock and access the protected data.

Yes, you must install git-crypt separately alongside git to perform encrypted backups. The scripts rely on git-crypt to manage encryption and require proper repository setup as well as secure handling of exported keys to unlock and restore data.

The best way to restore encrypted backups on a new machine is to import the previously exported git-crypt keys. Once unlocked, you can access the workspace and configuration data from the private repositories using the documented restoration steps.

Yes, you can back up workspace data and configuration to separate private GitHub repositories. The backup automation applies repository-specific encryption keys to each repository to keep the encrypted data isolated and secure.