769c633518
Create comprehensive task for granting Claude (The Chronicler) full API and SSH access to all Firefrost infrastructure. Task #65: Grant Claude Full Infrastructure Access (API + SSH) - Time: 30-45 minutes - Priority: HIGH - Status: PENDING Access Needed: 1. Gitea API token (admin scopes) - Create issues, add users, manage repos 2. SSH access to all 6 servers - Verify configs, restart services, troubleshoot 3. Service API tokens (optional) - Plane, Mailcow, Pterodactyl, Ghost Current Limitations Claude Has: - Can commit to Git (via Git token) ✅ - CANNOT create Gitea issues (must make templates) ❌ - CANNOT add Gitea users ❌ - CANNOT SSH to servers ❌ - CANNOT restart services ❌ After Task #65 Complete: - Claude creates Gitea issues directly ✅ - Claude adds users on request ✅ - Claude SSHs to all 6 servers ✅ - Claude restarts services when needed ✅ - Claude executes autonomous deployments ✅ Implementation: - Generate ed25519 SSH key pair - Distribute public key to all 6 servers - Store private key in Vaultwarden (Task #6) - Generate Gitea API token with full admin scopes - Test SSH access on all servers - Test Gitea API by creating test issue - Document all access in infrastructure manifest Security: - ed25519 SSH key (modern, secure) - All tokens stored in Vaultwarden (encrypted) - All actions logged and auditable - Keys can be revoked in < 5 minutes if needed Expected Benefits: - Force multiplication (Claude executes directly, not via templates) - Time savings: 2-4 hours/week of Michael's time - Faster response to issues - Autonomous routine operations - Better documentation (Claude documents as it works) Why This Matters: Turns Claude from 'documentation assistant' into 'operational partner' who can execute directly instead of creating work for Michael. Example: User asks 'add me to Gitea' → Claude does it immediately instead of creating template for Michael to execute later. Documentation: docs/tasks/claude-infrastructure-access/README.md - Complete implementation guide - SSH key generation steps - Gitea API token creation - Security considerations - Verification checklist - Break-glass revocation procedure For children not yet born. 💙🔥❄️ Created by: The Guide (Chronicler #35)
🔥❄️ 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. |