I disagree, you’ll have your backups, so even if everything breaks you will have a failsafe. If you get compromised it’s still not an issue: Everything server side is encrypted, the safety is in the clients and your master password length.
So, I see no particular differences with other services. Considering I hear of some issues with bitwarden servers that are constantly under attack, selfhosting could even increase the availability.
I got it working in my local Kubernetes cluster, by writing all the yml files myself. Then realized someone built a Helm chart for it, which is much easier to maintain. The hardest part was generating the TLS cert.
fraydabson@sopuli.xyz 1 year ago
I’ve considered this. Since I use it. I always read how people say that’s the one thing they rather leave to the pros lol
aesir@lemmy.world 1 year ago
I disagree, you’ll have your backups, so even if everything breaks you will have a failsafe. If you get compromised it’s still not an issue: Everything server side is encrypted, the safety is in the clients and your master password length.
So, I see no particular differences with other services. Considering I hear of some issues with bitwarden servers that are constantly under attack, selfhosting could even increase the availability.
fraydabson@sopuli.xyz 1 year ago
Yeah that’s a good point. I don’t see why not. Thanks I’ll probably give it a shot.
NegativeLookBehind@kbin.social 1 year ago
I got it working in my local Kubernetes cluster, by writing all the yml files myself. Then realized someone built a Helm chart for it, which is much easier to maintain. The hardest part was generating the TLS cert.