2ae7ee263f
WHAT WAS DONE: - Built browser dashboard (dashboard.html) showing installed vs latest version for all Pterodactyl game servers - Built PHP proxy (proxy.php + config.php) for Billing VPS deployment - Created isolated Nginx server block (version-proxy.conf) - Created full deployment guide (DEPLOYMENT-GUIDE.md) ARCHITECTURE: - PHP proxy at /var/www/version-proxy on Billing VPS (38.68.14.188) - Isolated from Paymenter/Laravel routing — separate directory + port - API keys (Pterodactyl ptlc_, CurseForge) live server-side only - FTB packs: fully automatic via .manifest.json + FTB public API - CurseForge packs: reads manifest.json, needs CF Project ID + API key - config.php blocked from direct web access via Nginx PENDING AT DEPLOYMENT: - Verify port 8080 is free (ss -tlnp) before enabling Nginx block - Fill real API keys into config.php on server - Enter CurseForge Project IDs for CF packs (saved in localStorage) COLLABORATION: - PHP proxy architecture designed by Gemini (consultation session 2026-03-29) - Dashboard HTML and detection logic by Chronicler #47 - Gemini identified Laravel routing conflict and content-type gotcha WHY: - Interim solution before full Blueprint extension (post-launch) - Hands-off modpack update monitoring for staff - Zero manual checking required after initial CF Project ID setup Signed-off-by: claude@firefrostgaming.com
🔥❄️ 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. |