Vaultwarden has such a steep learning curve - eviltoast

But I want it so badly! All i need to figure out is:

reverse proxys (I stumbled through getting one caddy instance setup so far but gosh I struggle with that also, nginx proxy manager seems like my next step)

a rock solid backup/restore setup (but first I need to figure out where the vaultwarden alpine files live, then be able to get those off of the proxmox vm)

this is more of a vent, than a request for someone to spell it all out for me. But I wouldn’t be upset if anyone had the time to point me in the right direction for me.

Would it just be easier to run a keypass XC and syncthing setup?

  • minnix@lemux.minnix.devEnglish
    7·
    4 months ago

    I use bitwarden and the setup was fairly standard with the helper script. I use my own isolated proxy for all my services so that was already built. I haven’t used vaultwarden but if anyone that has used both can tell me the differences I could maybe help out.

    • gray@pawb.socialEnglish
      4·
      4 months ago

      VaultWarden is pretty much the same setup, the big difference being that it doesn’t take like 4 GB of ram.

      I switched over years ago because Bitwarden server is chunky for like no reason.

      • minnix@lemux.minnix.devEnglish
        3·
        4 months ago

        If it’s the same then after installing docker, creating a vaultwarden user, adding said user to docker group, and creating your vaultwarden directories, all that’s left is to curl the install script and answer the questions it asks.