ZeasyAlex/GSM
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Fix CLAUDE.md: repo holds GSM app code, deploy is via Gitea Actions

Browse Source 
- Repository Purpose: it's not docs-only — the repo holds the GSM app
  (gsm-backend/, gsm-frontend/) plus docs/.
- Deployment: corrected "GitHub" to the actual Gitea remote
  (git.zeasy.dev) and Gitea Actions pipeline (.gitea/workflows/deploy.yml),
  which builds the frontend and copies to the server itself.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Alexander Zielonka
2026-06-26 19:39:58 +02:00
parent 024d97e544
commit 1db72ce92f
1 changed files with 13 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
CLAUDE.md
View File

@@ -4,7 +4,12 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
## Repository Purpose
This is a documentation repository for a homelab infrastructure. It contains technical documentation for servers, services, and network configuration - no application code.
This repository holds the **Gameserver Monitor (GSM)** web application together with the homelab documentation:
- `gsm-backend/` — Node.js + Express API (the GSM server)
- `gsm-frontend/` — React + Vite + TailwindCSS frontend
- `docs/` — technical documentation for the homelab servers, services, and network configuration
The deployed app runs at `/opt/gameserver-monitor/` on the monitor LXC (192.168.2.30).
## Infrastructure Overview
@@ -69,12 +74,14 @@ ssh root@192.168.2.30 'curl -X POST http://localhost:3000/api/servers/discord/in
## Deployment
**WICHTIG: NIEMALS per SCP deployen!** Alle Änderungen am GSM-Code müssen:
1. Lokal committed werden
2. Auf GitHub gepusht werden
3. Das CI/CD-System deployt automatisch auf den Server
Deployt wird über **Gitea Actions** (`.gitea/workflows/deploy.yml`); Remote ist `origin` = `https://git.zeasy.dev/ZeasyAlex/GSM.git`.
Kein manuelles Kopieren von Dateien per SCP, rsync oder ähnlichem!
**WICHTIG: NIEMALS manuell per SCP/rsync deployen!** Alle Änderungen am GSM-Code müssen:
1. Lokal committed werden
2. Auf den `main`-Branch (Gitea-Remote `origin`) gepusht werden
3. Die Pipeline baut das Frontend (`npm run build`) und deployt Backend + `dist/` automatisch auf den Monitor (192.168.2.30), danach `pm2 restart gsm-backend`
Der Deploy triggert nur bei Änderungen unter `gsm-backend/**` oder `gsm-frontend/**`. Das Kopieren auf den Server übernimmt ausschließlich die Pipeline (per `scp-action`) — kein manuelles SCP/rsync.
## Language Note