6c49e87f7b
Created complete configuration guide for Vaultwarden setup (450+ lines): Configuration Strategy: - Part A: SSH key setup (5 min) - Part B: Organization setup (25 min) - Part C: Security best practices - Part D: Cleanup and documentation Organization Structure: - Organization: Firefrost Gaming (Free plan, 2 users) - Users: Michael (owner) + Meg (admin/manager) - Collections: 6 total with granular permissions Collections Defined: 1. Server Credentials (Michael owner, Meg read-only) 2. API Keys & Tokens (Michael owner, Meg read-only) 3. Social Media Accounts (Both can edit) 4. Game Server Admin (Both can edit) 5. Billing & Financial (Michael owner, Meg read-only) 6. Staff & Shared Tools (Both can edit) Security Features: - SSH key authentication option - Two-factor authentication (2FA) setup - Strong master password policy - Secure password generator settings - Backup and recovery procedures Migration Process: - Step-by-step credential migration from personal vault - Verification of Meg's access - Cleanup of temporary credential files - Git repository sanitization Comprehensive troubleshooting for common issues. Unblocks: Scoped Gitea Token, all credential management workflows Ready to configure when Vaultwarden is deployed. Task: Vaultwarden Setup (Tier 1) FFG-STD-002 compliant
Tasks Directory
This directory contains task-specific documentation following the Task Documentation Standard (FFG-STD-002).
Each task gets its own subdirectory with:
- README.md (task overview)
- deployment-plan.md (how to build/deploy)
- usage-guide.md (how to use after deployed)
- troubleshooting.md (common issues)
- Other task-specific documentation as needed
See: docs/standards/task-documentation-standard.md for complete standard.
Current Tasks:
whitelist-manager/- Web dashboard for managing Minecraft server whitelists
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️