A Church Workday, a Roofing Company Rescue, and Opening Up Write Access in My Credential Manager
A full day: my regular weekly workday at the church, an afternoon trip to Precision Roofing in Beach Park to bring a server back online, an evening video session at Upload Partners, and — worked in alongside all of it — expanding my own credential manager so it can safely write new credentials, not just read the ones already there.
My weekly workday at the church
I spent 10:00 a.m. to 4:00 p.m. at the church for my regular weekly workday — the ongoing volunteer IT work that keeps their systems running week to week.
A down server at Precision Roofing
At 4:30, I drove out to Precision Roofing in Beach Park to deal with a server that wasn't coming online. Got it back up and running for them so they could get back to work.
An evening video session at Upload Partners
From 5:30 to 9:00 p.m., I was at Upload Partners for a video session.
Opening up write access in my credential manager
Alongside all of that, I kept working with my Claude Code assistant on cred, the
Vaultwarden-backed credential manager I've been building this month to replace a pile of scattered
plaintext credential files. Up to now it could only read credentials — today I opened it up to
safely create, update, and delete them too.
The first version of write access was deliberately locked down to one group of credentials, so nothing could land in the wrong place by accident. Today I asked for that restriction to come off, so I can target any of my real credential groups directly, with a sensible default if I don't specify one. That turned into a real back-and-forth — Claude Code itself pushed back hard on loosening a safety restriction inside a script that manages every credential I have, and it took me explicitly stepping in before it would proceed. I'd rather it be cautious about that than not.
Along the way, testing turned up two genuine bugs: the script was quietly leaving behind temporary files on certain failures, and some of those same failures weren't making it into the activity log at all. Both got fixed and checked with real create/update/delete tests against all three of my actual credential groups before any of it shipped. I also added a small safeguard for myself going forward: a command that double-checks any new group I register actually exists before it gets added, so a typo can't quietly poison the whole setup.