5a2eee40fb
CREATED: docs/guides/discord-bot-admin-panel.md (new comprehensive guide) - Complete implementation guide for web-based admin panel - Architecture section (credits Gemini for design decisions) - Security-first approach (dedicated firefrost-bot user, Discord OAuth2) - Zero-downtime config updates (in-memory + atomic disk writes) - Holly's usage guide (how to update role IDs via web interface) - Full troubleshooting section - Maintenance procedures Key Features Documented: - Discord OAuth2 authentication (no passwords) - Whitelist authorization (Holly + Michael only) - Role ID validation (regex + Discord API verification) - Atomic file writes with backup strategy - In-memory config updates (no bot restart needed) - Audit logging to Discord channel - HTTPS via Nginx + Let's Encrypt Status: Awaiting backend/frontend code from Gemini UPDATED: docs/guides/subscription-automation-guide.md - Task 9 rewritten to reference new admin panel guide - Added Option A (admin panel) vs Option B (manual SSH) paths - Removed SSH instructions for Holly (she won't have access) - Removed bot token from credentials file (security) - Updated Holly's tasks section with admin panel option - Preserved manual method as fallback Why These Changes: - Admin panel gives Holly independence (no waiting for Michael) - Cleaner separation of concerns (setup vs usage) - Security improvement (no SSH access needed for Holly) - Better documentation structure (1000+ line guide split logically) Architecture Credit: Gemini (Google AI) consultation on March 23, 2026 Chronicler #40
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Five Consultants — Jack, Oscar, Jasmine, Butter, Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |