firefrost-gaming/firefrost-operations-manual

Files

Claude e81a1b0df5 docs: create Cockpit deployment task for Chromebook workflow

Complete deployment plan for installing Cockpit web terminal on all 5 remaining servers (Command Center, Billing VPS, Panel VPS, TX1, NC1). Ghost VPS already has Cockpit operational.

Files created:
- docs/tasks/cockpit-deployment/README.md - Task overview
- docs/tasks/cockpit-deployment/deployment-plan.md - Technical strategy
- docs/tasks/cockpit-deployment/installation-commands.md - Copy/paste micro-blocks

Why: Enable full server management from Chromebook without SSH dependency. Claude sessions block port 22, but Cockpit (port 9090) works perfectly.

Estimated time: ~1 hour for all 5 servers (~10 min each)

Signed-off-by: The Chronicler <claude@firefrostgaming.com>

2026-03-21 06:43:16 +00:00

2.9 KiB

Raw Blame History

Task: Deploy Cockpit Web Terminal to All Servers

Overview

Deploy Cockpit (web-based server management) to all 5 Firefrost servers that don't have it yet. This enables full server management from Michael's Chromebook without SSH client dependency.

Current Status

Has Cockpit:

✅ Ghost VPS (64.50.188.14:9090)

Needs Cockpit:

❌ Command Center (63.143.34.217)
❌ Billing VPS (38.68.14.188)
❌ Panel VPS (45.94.168.138)
❌ TX1 Dallas (38.68.14.26)
❌ NC1 Charlotte (216.239.104.130)

Why This Matters

Problem: Claude sessions block SSH (port 22), forcing reliance on existing Cockpit for Ghost VPS work.

Solution: Cockpit on all servers = Chromebook can manage entire infrastructure via browser.

Benefits:

No SSH client needed
Works on Chromebook natively
Web terminal + service management + resource monitoring
Port 9090 standard across all servers
Lightweight (~50MB RAM per server)

Files in This Task

README.md (this file) - Task overview
deployment-plan.md - Complete deployment strategy and technical details
installation-commands.md - Copy/paste ready commands in micro-blocks

How to Execute

Recommended Approach

Read deployment-plan.md - Understand the full strategy
Pick a server to start with (suggest Command Center first)
SSH into that server (or use existing Cockpit if available)
Follow installation-commands.md - Copy/paste each block in order
Test the Cockpit URL in browser
Repeat for remaining servers

Order Recommendation

Phase 1 (VPS tier - quick):

Command Center
Billing VPS
Panel VPS

Phase 2 (Dedicated tier): 4. TX1 Dallas 5. NC1 Charlotte

Time estimate: ~1 hour total (~10 min per server)

Success Criteria

All 6 servers accessible via https://IP:9090
Terminal tab functional on all servers
Services tab shows systemd units
System tab shows accurate resource usage
Michael can manage all servers from Chromebook

Security Notes

Cockpit is secure by default:

HTTPS only (self-signed certificates)
Uses existing PAM authentication
No new user accounts created
No new attack surface (reuses SSH auth)

Rollback

If any server has issues:

sudo systemctl stop cockpit.socket
sudo systemctl disable cockpit.socket

Complete removal if needed:

sudo apt remove --purge cockpit

Documentation Updates After Completion

Update infrastructure-manifest.md with Cockpit status
Add Cockpit URLs to server quick-reference
Update session-start docs with Chromebook access info

None (standalone infrastructure enhancement)

Blocks

None

Blocked By

None

Created: March 21, 2026 (Session 37 - The Chronicler)
Priority: HIGH (enables Chromebook workflow)
Estimated Time: 1 hour
Status: READY TO EXECUTE

2.9 KiB Raw Blame History