Rotate the leaked Gitea PAT + establish secrets management #11
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A
write:repositoryGitea PAT was exposed in a working session/transcript and must be revoked (git.mivanchenko.de → Settings → Applications). Rotate anything else that shared that exposure.Broader: real deployed secrets live scattered across per-service
.envfiles + the Caddyfile on the homelab. Introduce proper secrets management (e.g. Vaultwarden — already planned — orsops/age-encrypted env in the repo) so secrets have a single source of truth, are rotatable, and never sit in plaintext where they can leak.Acceptance: leaked PAT revoked; a documented secrets store + rotation runbook; repo confirmed free of plaintext secrets (
.gitignorealready covers.env,.secrets/).