Developer productivity tips for managing secrets
The fast path must be the safe path. If fetching a dev key takes two minutes, people paste it in Slack. Productivity advice here is security advice.
1. One naming scheme (document once)
<provider>_<purpose>_<environment>
See organize API keys and across projects.
2. One vault workspace per repo or product
Opening the app → workspace → copy beats grepping twelve .env.bak files.
PassStore is built around that mental model.
3. Shell discipline: dedicated tabs
Tab A: exports dev keys for api.
Tab B: exports for web.
Close tabs when done — avoids wrong DATABASE_URL incidents.
4. Makefile / justfile standard targets
.PHONY: dev
dev:
@test -n "$$DATABASE_URL" || (echo "Set DATABASE_URL in this shell"; exit 1)
npm run dev
Fails loud early instead of silent wrong DB.
5. CI copy-paste templates
New service? Clone last repo’s .github/workflows patterns with secret names already wired — developer setup 2026.
6. Incident muscle memory
Bookmark one internal runbook that links:
Panic shrinks when the path is pre-decided.