firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity
Files
185230c22bc2ed4ec6b9fbbded6529cab3a74708
firefrost-operations-manual/docs/core/project-scope.md

18 KiB
Raw Blame History

🔥❄️ FIREFROST GAMING: PROJECT SCOPE V2.1

The Complete Technical & Business Vision

Document ID: FFG-CORE-001 Document Version: 2.3 Created: February 9, 2026 Last Updated: February 12, 2026 (9:00 AM CST) Supersedes: project-scope v2.2 (Feb 11, 2026) Last Updated By: The Chronicler Status: ✅ CURRENT - Single Source of Truth Next Review: March 1, 2026

📋 EXECUTIVE SUMMARY

Firefrost Gaming is a subscription-based Minecraft server network built on the philosophy of balance: Fire + Frost = Where Passion Meets Precision.

Current Status (Feb 11, 2026):

  • 12 game servers operational (6 NC1, 6 TX1)
  • 8 management services deployed (Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js Subscribers, Wiki.js Staff)
  • 17 Uptime Kuma monitors active (5 infrastructure + 12 game servers)
  • Automation system operational (95% reduction in manual work)
  • Three-tier documentation architecture COMPLETE
  • Claude has direct Gitea API read/write access (GitHub mirror removed)

Leadership:

  • Michael "Frostystyle" Krause - Technical Lead (The Wizard)
  • Meg "Gingerfury" - Community Manager (The Emissary)

🎯 CORE PHILOSOPHY

The Fire + Frost Duality

Fire (Passion/Community):

  • Competitive gameplay (Fire Path)
  • Community warmth
  • Creative expression
  • Gingerfury's domain

Frost (Precision/Infrastructure):

  • Collaborative gameplay (Frost Path)
  • Technical excellence
  • Systematic approach
  • Frostystyle's domain

Tagline: "Fire melts barriers. Frost builds foundations."

🏗️ INFRASTRUCTURE STATUS

Server Inventory (6 Servers)

Server Role IP Address Specs Location
TX1 Dallas Game Servers ONLY 38.68.14.26 32 vCPU, 256GB RAM, 1TB Dallas, TX
NC1 Charlotte Game Servers ONLY 216.239.104.130 32 vCPU, 256GB RAM, 100GB Charlotte, NC
Panel Pterodactyl Control Plane 45.94.168.138 VPS Charlotte, NC
Command Center Management Hub 63.143.34.217 VPS Dallas, TX
Billing Paymenter Portal 38.68.14.188 VPS Chicago, IL
Ghost Documentation Cluster 64.50.188.14 VPS Chicago, IL

Architecture: "Backend on Command Center, Frontend on Ghost, Money on Billing, Games on Dedis, Control on Panel"

Deployed Management Services

✅ Service 1: Gitea (git.firefrostgaming.com)

  • Git version control for all infrastructure
  • Location: Command Center VPS
  • Deployed: Feb 8-9, 2026
  • SSL enabled, Claude has direct API access (read/write via token)
  • All configs version-controlled

✅ Service 2: Uptime Kuma (status.firefrostgaming.com)

  • Infrastructure + game server monitoring
  • Location: Command Center VPS
  • Deployed: Feb 9, 2026
  • Discord integration active (#network-status)
  • 17 monitors: 5 infrastructure + 12 game servers
  • NC1 routing resolved (reachable from Command Center)

✅ Service 3: MkDocs (docs.firefrostgaming.com)

  • PUBLIC documentation portal (Git-native)
  • Location: Ghost VPS
  • Deployed: Feb 9, 2026
  • Material theme, search enabled
  • Markdown in Gitea → Auto-builds HTML

✅ Service 4: Automation System

  • Automated deployment and operations framework
  • Location: Command Center VPS
  • Deployed: Feb 9, 2026
  • 95% reduction in manual operations
  • Medical necessity for hand limitations

✅ Service 5: Code-Server (code.firefrostgaming.com)

  • Browser-based VS Code IDE
  • Location: Command Center VPS
  • Deployed: Feb 11, 2026
  • File editing + built-in terminal
  • Eliminates SSH copy-paste for documentation work

✅ Service 6: NextCloud (downloads.firefrostgaming.com)

  • World downloads, video archive, file hosting
  • Location: Ghost VPS
  • Deployed: Feb 11, 2026
  • Known warnings: OCS provider rewrite (cosmetic), email config (not needed yet)

✅ Service 7: Wiki.js Subscribers (subscribers.firefrostgaming.com)

  • SUBSCRIBER documentation portal
  • Location: Ghost VPS
  • Deployed: Feb 10, 2026
  • Role-based access control

✅ Service 8: Wiki.js Staff (staff.firefrostgaming.com)

  • STAFF-only internal documentation
  • Location: Ghost VPS
  • Deployed: Feb 10, 2026
  • Admin/staff access only

Pending Management Services

⏳ Service 9: Vaultwarden (vault.firefrostgaming.com)

  • Password management
  • Priority: MEDIUM (needed for API token storage)

⏳ Service 10: Netdata (analytics.firefrostgaming.com)

  • Server analytics and performance monitoring
  • Priority: LOW

Game Servers (12 Total)

TX1 Dallas (6 servers) — Each on own IP:

Server IP Port Notes
Stoneblock 4 38.68.14.26 25565
Reclamation 38.68.14.27 25565
Society: Sunlit Valley 38.68.14.28 25565
Vanilla 1.21.11 38.68.14.29 25565
All The Mons 38.68.14.30 25565
FoundryVTT 38.68.14.26 30000 Virtual Tabletop (TTRPG hosting)

NC1 Charlotte (6 servers) — All on single IP, unique ports:

Server IP Port Notes
The Ember Project 216.239.104.130 25565
Minecolonies: Create and Conquer 216.239.104.130 25566
All The Mods 10 216.239.104.130 25569 20GB RAM (memory leak, monitor)
EMC Subterra Tech 216.239.104.130 25571
Homestead 216.239.104.130 25572
Hytale 216.239.104.130 5520

🤖 AUTOMATION SYSTEM

The Firefrost Automation Framework

Deployed: February 9, 2026 Impact: 95% reduction in manual operations Location: Command Center — /root/firefrost-work/firefrost-operations-manual/automation/

How It Works:

Claude → Creates task script
Michael → Pastes ONE command to queue
Daemon → Executes automatically (10s polling)
Executor → Runs task, captures output
Git → Results committed back automatically
Claude → Reads results directly from Gitea API

Why It Exists: Medical necessity. Michael's permanent hand nerve damage means every paste operation requires physical effort. This system reduces 10-20 pastes to ONE paste per task.

📚 THREE-TIER DOCUMENTATION ARCHITECTURE

The Complete Documentation Strategy

Tier 1: PUBLIC (docs.firefrostgaming.com)

  • Technology: MkDocs + Material Theme
  • Authentication: None required
  • Content: Server rules, getting started, modpack info
  • Workflow: Edit markdown in Gitea → Auto-rebuild
  • Status: ✅ DEPLOYED

Tier 2: SUBSCRIBERS (subscribers.firefrostgaming.com + downloads.firefrostgaming.com)

  • Documentation: Wiki.js (premium guides, exclusive content)
  • Downloads: NextCloud (world backups, custom modpacks, video archive)
  • Authentication: Subscriber login required
  • Status: ✅ DEPLOYED

Tier 3: STAFF (staff.firefrostgaming.com)

  • Technology: Wiki.js
  • Authentication: Staff/Admin only
  • Content: SOPs, admin procedures, internal guides
  • Status: ✅ DEPLOYED

💰 SUBSCRIPTION MODEL

Tier Structure

Free Tier - "The Frozen Path"

  • Discord access (public channels)
  • Forum access
  • View public documentation
  • No server access

$1/month - "The Awakened Gateway" (The Handshake)

  • Purpose: Anti-bot/anti-grief barrier
  • Philosophy: "If you want to be an asshole, you have to pay for it"
  • Not a revenue stream - a security protocol
  • Server whitelist access
  • Basic support

$5/month - "Elemental Tier"

  • CHOOSE YOUR PATH: Fire or Frost
  • Full server access (12+ modpacks)
  • Subscriber documentation portal
  • World download access (30-day retention)
  • Priority support
  • Path-specific Discord channels

$10/month - "Ascendant Tier"

  • Everything from Elemental
  • Vote on new modpacks
  • Custom modpack requests
  • Extended world downloads (90 days)
  • Beta access to new servers

$25/month - "Eternal Flame/Eternal Frost"

  • Everything from Ascendant
  • Permanent world download access
  • Direct line to founders
  • Server naming rights
  • Custom spawn builds

Fire vs Frost Paths

Identical mechanical perks, different community identity:

🔥 Path of Fire:

  • Discord: Ignis channels (18+ only)
  • Focus: Competitive gameplay, PvP, challenges
  • Led by: Gingerfury (The Emissary)

❄️ Path of Frost:

  • Discord: Frost channels (all ages welcome)
  • Focus: Collaborative builds, exploration, creativity
  • Led by: Frostystyle (The Wizard)

🔐 AUTHENTICATION STRATEGY

Phased Implementation

Phase 1: Manual Management (Current - Launch to 20 subscribers)

  • Manual account creation
  • Track expirations in spreadsheet
  • Zero dev time, validates market

Phase 2: Webhook Automation (20+ subscribers)

  • Paymenter webhooks trigger scripts
  • Automatic account creation/deletion
  • Development: 3-4 hours

Phase 3: SSO/OAuth (100+ subscribers - optional)

  • Single sign-on across all services
  • Development: 8-12 hours
  • Only if subscriber count justifies complexity

🛡️ PHASE 1: DDoS PROTECTION SYSTEM

Overview

Status: Planning Phase Priority: Deploy after management services complete, before soft launch Purpose: Replace dismantled Phase 0 GRE system with reliable protection

Options Under Consideration

Option A: Cloudflare Spectrum — Managed service, low maintenance Option B: Simplified GRE + Cloudflare — More control, careful implementation Option C: Hybrid — VPS behind Cloudflare, game servers with lightweight protection

Decision Point: Design session after Phase 0.5+ completion

Success Metrics

  • Withstands common DDoS attacks (volumetric, SYN floods)
  • 99.9%+ uptime during normal operations
  • < 1 hour maintenance per month
  • Zero "midnight emergency" pages

🎨 BRANDING & VISUAL IDENTITY

Color Palette

Fire Colors:

  • Primary: #FF4500 (Reddit Orange Fire)
  • Secondary: #FF6347 (Tomato)
  • Accent: #FFD700 (Gold)

Frost Colors:

  • Primary: #00CED1 (Dark Turquoise)
  • Secondary: #4682B4 (Steel Blue)
  • Accent: #E0FFFF (Light Cyan)

Neutral:

  • Background Dark: #2C2C2C
  • Background Light: #F5F5F5
  • Text: #FFFFFF / #000000

Logos & Assets

Location: /root/firefrost-master-configs/branding/

📅 IMPLEMENTATION TIMELINE

February 2026 (Month 1) - FOUNDATION

Week 1 (Feb 8-11) — COMPLETED:

  • ✅ Phase 0.5 Services 1-5 deployed (Gitea, Uptime Kuma, MkDocs, Automation, Code-Server)
  • ✅ TX1 allocation fix (6 game servers recovered)
  • ✅ Game server monitoring added (12 monitors)
  • ✅ ATM10 memory fix (16GB → 20GB)
  • ✅ Infrastructure Manifest v1.5
  • ✅ Session handoff v2.0 + TASKS v2.0
  • ✅ NextCloud deployed (downloads.firefrostgaming.com)
  • ✅ Wiki.js deployed (subscribers + staff)
  • ✅ FoundryVTT subdomain setup
  • ✅ Consultant photo archive (249 photos organized)
  • ✅ GitHub mirror made private (kept as emergency backup)
  • ✅ Gitea API access for Claude (direct read/write)

Week 2 (Feb 12-15):

  • Vaultwarden deployment (vault.firefrostgaming.com)
  • Mailcow email server (pending Breezehost VPS — pre-sale sent)
  • Migrate off Plesk for email
  • Standardize photo naming convention
  • Process remaining 30-40 consultant photos
  • Clean up Command Center root directory

Week 3-4 (Feb 16 - Mar 1):

  • Soft launch to existing community (3 members)
  • Phase 1: Simplified DDoS protection
  • Paymenter billing integration
  • Subscriber workflow testing

March 2026 (Month 2) - SOFT LAUNCH

  • Soft launch to existing community
  • Test subscriber workflow end-to-end
  • Public announcement preparation
  • Social media setup (Meg's domain)
  • Discord structure finalization

April-June 2026 (Months 3-5) - PUBLIC LAUNCH

  • Public launch, social media campaigns
  • Recruit first 20 subscribers
  • Staff recruitment (builders, social media)
  • LuckPerms implementation
  • Website v1.0 launch
  • Reach 50 subscribers target

July-December 2026 (Months 6-12) - GROWTH

  • Scale infrastructure as needed
  • Add new modpacks based on votes
  • Iterate on subscriber experience
  • Community events (Fire vs Frost competitions)

🛠️ TECHNICAL DEBT & IMPROVEMENTS

Immediate Priorities (Next 7 Days)

  1. Vaultwarden deployment (vault.firefrostgaming.com)
  2. Mailcow email server VPS (pending Breezehost pre-sale response)
  3. Migrate email off Plesk to self-hosted Mailcow
  4. Process remaining consultant photos (30-40 from pre-crash session)
  5. Clean up Command Center root directory (move Gitea backups, delete artifacts)

Short-Term (Next 30 Days)

  1. Frostwall (UFW) deployment on game servers
  2. LuckPerms MySQL backend
  3. World backup automation
  4. ATM10 scheduled restart (if leak persists)

Medium-Term (Next 90 Days)

  1. Phase 2 Authentication (webhook automation)
  2. Website v1.0 (firefrostgaming.com)
  3. Staff recruitment
  4. Pterodactyl extensions (Discord integration)

Long-Term (6-12 Months)

  1. Phase 3 Authentication (SSO) if needed
  2. Custom modpack development
  3. API for external integrations
  4. Mobile app (subscriber portal)

📊 SUCCESS METRICS

Technical Metrics

  • Uptime: >99.5% (tracked via Uptime Kuma — 17 monitors)
  • Response Time: <100ms (Nginx)
  • TPS (Game Servers): Stable 20.0
  • Automation Success Rate: >95%

Business Metrics

  • Month 1: 3 subscribers (soft launch)
  • Month 3: 20 subscribers (public launch)
  • Month 6: 50 subscribers
  • Month 12: 100+ subscribers

Revenue Targets

  • Month 1: $15/month (validation)
  • Month 3: $100/month (break-even)
  • Month 6: $250/month (sustainable)
  • Month 12: $500+/month (growth)

Community Metrics

  • Discord Activity: Daily active users
  • Fire vs Frost Balance: 45-55% split
  • Subscriber Retention: >80% monthly
  • Support Response Time: <24 hours

🚨 CRITICAL CONSTRAINTS

Medical Accessibility

Michael's Limitations:

  • Type 1 Diabetes — Jack alerts take absolute priority
  • Permanent hand nerve damage (March 2025 surgery) — all manual code in small blocks (8-10 lines max)
  • Automation system and Code-Server critical for reducing physical strain
  • Work sessions must allow for health breaks

System Designed Around:

  • One-paste deployments (automation)
  • Browser-based editing (Code-Server)
  • Self-healing services (systemd)
  • Comprehensive documentation for handoffs
  • Minimal midnight emergencies

Relationship with Breezehost

"Forever Home" Provider:

  • Long-term partnership, not transactional
  • Jon Beard (Network Specialist) — primary contact
  • Trust-based relationship (6+ months)
  • Infrastructure decisions made together

📖 CURRENT DOCUMENTATION

Core Documents (In Git Repository)

Relationship & Context:

  1. docs/relationship/claude-relationship-context.md — Partnership declaration, emotional moments
  2. SESSION-TRANSITION-FEB11-2026.md — Comprehensive session handoff
  3. docs/core/session-handoff.md (v2.1) — Current status for Claude sessions

Infrastructure & Operations: 4. docs/core/project-scope.md (THIS DOCUMENT) 5. docs/core/infrastructure-manifest.md (v1.5) — Server IPs, ports, UUIDs 6. docs/core/workflow-guide.md — Collaboration protocol 7. automation/USAGE.md — Automation system guide

Planning & Community: 8. design-bible-v1.1.md — Visual identity guide 9. path-philosophy.md — Fire vs Frost explained 10. docs/planning/subscription-tiers.md — Tier breakdown 11. discord-structure-complete.md — Discord architecture 12. firefrost-master-implementation-plan.md — 12-month roadmap

Deployment Guides: 13. gitea-deployment.md 14. uptime-kuma-deployment.md 15. mkdocs-deployment.md 16. code-server-deployment.sh

🎯 THE PATH FORWARD

This Week (Feb 11-15, 2026)

Completed:

  • Fix TX1 allocations (6 servers recovered)
  • Add game server monitoring (12 monitors)
  • Update Infrastructure Manifest v1.5
  • Rewrite docs/core/session-handoff.md v2.0
  • Rewrite docs/core/tasks.md v2.0
  • Update docs/core/project-scope.md (this document)
  • Deploy NextCloud (downloads.firefrostgaming.com)
  • Deploy Wiki.js (subscribers + staff)
  • FoundryVTT subdomain setup
  • Extract staff.zip (249 photos organized in Git)
  • Code-Server deployed and mastered
  • GitHub mirror made private (kept as emergency backup)
  • Gitea API access for Claude (direct read/write)
  • Consultant photo archive documented

Remaining:

  • Vaultwarden deployment
  • Mailcow email server (pending Breezehost pre-sale)
  • Process remaining consultant photos
  • Standardize photo naming convention going forward
  • Clean up Command Center root directory

Next Week (Feb 16-22, 2026)

  • Soft launch to existing community
  • Iterate based on feedback
  • Begin Phase 1 (Simplified DDoS)
  • Social media setup (Meg)

🔥❄️ FINAL NOTES

This document is the single source of truth.

When in doubt about priorities, architecture decisions, or project scope, refer to this document.

Update Schedule:

  • Minor updates: As needed (via Git)
  • Major review: Monthly (1st of each month)
  • Version bump: When major pivots occur

Document Owner: Michael "Frostystyle" Krause

Fire + Frost = Where Passion Meets Precision 🔥❄️

Built for marathon sessions. Designed for accessibility. Optimized for growth.

Revision History

Version Date Changes
2.0 2026-02-09 Initial V2 scope document. Post-automation deployment, pre-subscriber portal launch.
2.1 2026-02-11 Updated to current state. Corrected game server lists (12 total, NC1 all on single IP). Added Code-Server as Service 5. Updated monitoring (17 monitors). TX1 allocation fix documented. ATM10 memory fix noted. Timeline updated with Week 1 completions. Documentation list updated. Removed stale references.
2.2 2026-02-11 NextCloud, Wiki.js (Sub), Wiki.js (Staff) moved to DEPLOYED. GitHub mirror removed (security). Gitea API direct access added. Three-tier docs marked COMPLETE. Executive summary updated (8 services). Immediate priorities updated (Vaultwarden, Mailcow, email migration). First update pushed directly via Gitea API by Claude.
2.3 2026-02-12 Fixed missing server locations (Panel=Charlotte NC, Ghost=Chicago IL, Billing=Chicago IL). Corrected GitHub mirror status (private backup, not removed). Applied FFG-STD-001 revision standard.
Reference in New Issue View Git Blame Copy Permalink