ee7fbabf7e
🚨 BLOCKS SOFT LAUNCH - Must complete before accepting first subscriber Created comprehensive task documentation for automating subscriber provisioning between Paymenter billing and Pterodactyl Panel. Problem: - Currently every new subscriber requires manual Pterodactyl account creation - Tier changes require manual permission updates - Cancellations require manual cleanup - Does NOT scale beyond 5-10 subscribers Solution: Automated webhook bridge: Paymenter → Integration → Pterodactyl API Customer subscribes → server access granted in 30 seconds (zero touch) Task includes: - 4 integration options to investigate (native extensions vs custom) - Pterodactyl API setup guide with required permissions - 10-tier subscription mapping (Awakened → Founder) - Webhook configuration and security - Full lifecycle testing requirements (create/upgrade/cancel) - Success criteria checklist (4 phases) - Error handling and logging requirements - Manual override procedure for edge cases Research priority: 1. Check Paymenter docs for native Pterodactyl integration 2. Check Blueprint marketplace for Paymenter module 3. Fall back to n8n workflow if no native option 4. Last resort: custom webhook script Time estimate: 4-6 hours Priority: CRITICAL (Tier 0 - blocks soft launch) Status: 🔴 BLOCKING SOFT LAUNCH Related: - Task #2 (LuckPerms Discord sync - depends on this) - Blocks acceptance of real subscribers Documentation: docs/tasks/paymenter-pterodactyl-integration/README.md Added to docs/core/tasks.md as Task #83 Created by: The Verifier (Chronicler #41) Session: March 26, 2026, 2:20 AM CST
🔥❄️ 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. |