Tips Sharing: Automatic Backup to GitHub Repository (No server needed)

Ask the Community Password Manager
, ,
1

Backup JSON to GitHub repository, automated via GitHub Actions.
GitHub account is all your need.

Visit: GitHub - x-o-y/backup-vaultwarden-publish: 1. Backup vaultwarden/bitwarden JSON data to GitHub's repo; 2. import latest JSON to another vault account.
An open-source solution.

flowchart TB
    subgraph B[Backup new changes only]
        direction LR
        actions@{shape: hex, label: "GitHub Actions"}
        repo[GitHub Repository]
        backups@{ shape: docs, label: "JSON backups<br>Timestamped"}
        actions -->repo --> backups
    end

    A[ Source <br> Bitwarden/Vaultwarden <br> Account] -- export encrypted JSON --> B
    B -. purge & import to .-> C[Destination <br> Vaultwarden/Bitwarden <br> Account]
2

@xplusyi Welcome to the forum!

Is this targeted at developers for passwordless solutions? Because if not, please change the category to “password manager”.

1 Like
3

Thanks for reminding me.

However, I cannot find the ‘EDIT’ button since it was submitted…

4

I edited it now for you. I had to choose the three tags for “server”, “app” and “OS”, so please give feedback if the tags can remain as they are.

5

@xplusyi , Welcome to the community!

Struggling to understand the use-case here. There is a general rule that one should protect backups at least as well as the source-data is protected. If one is sufficiently uncomfortable using Bitwarden’s cloud vaults that they would chose to self-host, why would they be comfortable placing the exports in Github’s cloud?

Hoping the answer will help me better understand if there is more than just not wanting ones vault in the cloud that would cause one to self-host.

2 Likes
6

for me, there are two use cases:

  1. In case if your bitwarden/vaultwarden account data cannot be accessed or deleted by mistake, you can restore with the encrypted backups in GitHub – keep the encrypt key in a safe place.
  2. Also, if you have two bitwarden/vaultden accounts, you can use this to sync from the source to the destination.