docs: Update CLAUDE.md — Code now running locally on Nitro (April 15, 2026)
This commit is contained in:
16
CLAUDE.md
16
CLAUDE.md
@@ -1,10 +1,20 @@
|
||||
# Firefrost Gaming — Dev Panel Workspace
|
||||
# Firefrost Gaming — Local Nitro Workspace
|
||||
|
||||
## What This Is
|
||||
Dedicated development server (64.50.188.128) for Firefrost Gaming.
|
||||
Claude Code is now running locally on Michael's Nitro laptop (AN515-55).
|
||||
This repo is `firefrost-services` — all services, mods, and tools in one place.
|
||||
Git remote pushes to git.firefrostgaming.com (Gitea).
|
||||
|
||||
## Environment Change (April 15, 2026)
|
||||
Previously: Claude Code ran via SSH on Dev Panel (64.50.188.128) at `/opt/mod-builds/firefrost-services`
|
||||
Now: Claude Code runs locally on Nitro at `C:\Users\mkrau\firefrost-services`
|
||||
|
||||
**What this means:**
|
||||
- Java/Gradle builds are NOT available locally — mod compilation must be done on Dev Panel or dispatched via bridge
|
||||
- All three repos are cloned locally: `firefrost-services`, `firefrost-operations-manual`, `firefrost-website`
|
||||
- Workflow: edit locally → git push → Chronicler deploys to servers
|
||||
- The bridge protocol works the same way
|
||||
|
||||
## Projects
|
||||
- `services/rules-mod/` — Minecraft /rules command mod (3 versions)
|
||||
- `services/modpack-version-checker/` — ModpackChecker (Python CLI + Pterodactyl Blueprint extension)
|
||||
@@ -49,7 +59,7 @@ curl -u "mkrause612:APP_TOKEN" -T file.jar \
|
||||
**Source code:** `services/rules-mod/1.21.1/`, `1.20.1/`, `1.16.5/`
|
||||
|
||||
## Gemini Consultations (Reference Library)
|
||||
The operations manual is cloned at `/opt/mod-builds/firefrost-operations-manual/`.
|
||||
The operations manual is cloned at `C:\Users\mkrau\firefrost-operations-manual\` (local Nitro) or `/opt/mod-builds/firefrost-operations-manual/` (Dev Panel via SSH).
|
||||
Gemini architectural consultations are at `docs/consultations/` in that repo.
|
||||
When working on a project, check for relevant consultations BEFORE making architectural decisions.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user