Firefrost Automation ef3af6e343 Phase M3 COMPLETE: Uptime Kuma migrated to Command Center
Uptime Kuma successfully migrated from TX1 to Command Center VPS:
- Node.js upgraded (18.20.8 → 20.20.0) for compatibility
- All monitors operational at status.firefrostgaming.com
- Data preserved (kuma.db + config)
- SSL certificate configured
- 100% uptime on all monitored services

NEW BEST PRACTICE: Update Cloudflare DNS BEFORE running Certbot
- Prevents SSL cert validation failures
- Added to workflow-guide.md

Migration Progress: 3/3 services complete (Gitea, Automation, Uptime Kuma)
Total session time: 5.5 hours
Game server impact: ZERO
Data loss: ZERO

NC1 monitoring: Still excluded (datacenter routing limitation)

Remaining: Ghost VPS cluster (MkDocs, Wiki.js, NextCloud)

Command Center VPS now serving:
- git.firefrostgaming.com (Gitea)
- status.firefrostgaming.com (Uptime Kuma)
- Automation daemon (connected to Gitea)
2026-02-09 19:10:51 -06:00
2026-02-08 02:58:04 -06:00

Firefrost Phase 0 Configurations

Project: Frostwall Protocol - Infrastructure Archive
Status: Active
Repository Purpose: Version-controlled storage of all Firefrost Gaming infrastructure configurations

Repository Structure

  • docs/ - Technical documentation and deployment guides
  • management/ - Management service configurations (Gitea, etc.)
  • nodes/ - Node network configurations
  • security/ - Firewall and security rules
  • web/ - Nginx and web service configurations

Current Services

  • Gitea (git.firefrostgaming.com) - Version Control System

Maintained By

The Wizard (Claude) & Michael
Last Updated: February 8, 2026

Description
No description provided
Readme 1 GiB
Languages
Shell 70%
Python 16.2%
Nunjucks 8.6%
JavaScript 2.5%
HTML 2.4%
Other 0.3%