Moving 545 Passwords from Bitwarden's Cloud to Vaultwarden: the YubiKey Detour and the Count That Lied
For years I kept my password vault in Bitwarden’s cloud on a Premium subscription. It worked, it was cheap, and the clients were lovely. Then Bitwarden’s licensing direction this year gave me the nudge, on top of a reason I’d already settled on: I wanted the vault on hardware I own, behind my own TLS and my own backups.
The clients stay exactly the same. Vaultwarden speaks the Bitwarden API, so the browser extensions, desktop app and phone apps just get a new server URL — the change is where the bytes live, not how I touch them.
What follows is the honest version: a migration designed so my master password never passed through the AI assistant I do my homelab work with, a YubiKey detour of my own making, and three item counts for one vault that disagreed until I learned which to trust.
Two Ways My Self-Hosted Immich Broke — and Neither Was Corrupt Data
I self-host Immich for my photo library, and it has broken on me in two completely different ways — both instructive, and both sharing a reassuring punchline: the photos were always fine. The failures were in the plumbing around them, not the data.
The first was a storage problem wearing a data-corruption costume: thousands of “unsupported image format” and “input file is missing” errors for files that were perfectly healthy. The second was a self-inflicted supply-chain problem: an overnight auto-update yanked the database extension out from under the server and put it in a boot loop. This post is both stories, because together they’re a decent field guide to operating Immich in a homelab.
Backing Up a Homelab as Code: Docker Configs to a Private Git Repo, Without Leaking Secrets
If my main Docker host died tomorrow, how fast could I rebuild it? For a long time the honest answer was “slowly, and from memory.” The fix is to treat the box’s configuration as code: every docker-compose.yml, Dockerfile, and config file committed to a private git repo, so reimaging is a git clone and a handful of docker compose up commands.
The trap is that a live Docker tree is a minefield of secrets — .env files, TLS private keys, API tokens hardcoded into compose files — and pushing any of them to GitHub, even a private repo, is a bell you can’t fully un-ring. This post is the repeatable procedure I landed on: what to commit, what to never commit, and the automated checks that keep the second category out.