- Add 260124-nextcloud-maintenance.yml playbook for database indices and mimetypes - Add run-maintenance-all-servers.sh script to run maintenance on all servers - Update ansible.cfg with IdentitiesOnly SSH option to prevent auth failures - Remove orphaned SSH keys for deleted servers (black, dev, purple, white, edge) - Remove obsolete edge-traefik and nat-gateway roles - Remove old upgrade playbooks and fix-private-network playbook - Update host_vars for egel, ree, zwaan - Update diun webhook configuration Successfully ran maintenance on all 17 active servers: - Database indices optimized - Mimetypes updated (145-157 new types on most servers) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ssh | ||
| .gitignore | ||
| README.md | ||
Age Encryption Keys
⚠️ CRITICAL: This directory contains encryption keys that are NOT committed to Git.
Key Files
age-key.txt- Age private key for SOPS encryption (GITIGNORED)
Backup Checklist
Before proceeding with any infrastructure work, ensure you have:
- Copied
age-key.txtto password manager - Created offline backup (printed or encrypted USB)
- Verified backup can decrypt secrets successfully
Key Recovery
If you lose access to age-key.txt:
- Check password manager for backup
- Check offline backups (printed copy, USB drive)
- If no backup exists: Secrets are PERMANENTLY LOST
- You will need to regenerate all secrets
- Re-encrypt all
.sops.yamlfiles - Update all services with new credentials
Generating a New Key
Only do this if you've lost the original key or need to rotate for security:
# Generate new Age key
age-keygen -o age-key.txt
# Extract public key
grep "public key:" age-key.txt
# Update .sops.yaml in repository root with new public key
# Re-encrypt all secrets
cd ..
for file in secrets/**/*.sops.yaml; do
SOPS_AGE_KEY_FILE=keys/age-key.txt sops updatekeys -y "$file"
done
Security Notes
- This directory is in
.gitignore - Keys should never be shared via email, Slack, or unencrypted channels
- Always use secure methods for key distribution (password manager, encrypted channels)