FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Switch CLAUDE.md to reflect live dev/prod split

Browse Source
This commit is contained in:
Gmer4Lfe
2026-06-26 21:51:29 -04:00
parent f92ee4064b
commit 97dfd522d0
1 changed files with 6 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+6 -12
View File
@@ -2,28 +2,22 @@
## Working Rules (read first)
- **Workspace is always** `/boot/config/plugins/varaverk` — every edit goes here.
- **Dev workspace** — `/mnt/cloud-storage/Important Shit/Git/Development/Varaverk/`. All editing happens here.
- **Prod** — `/boot/config/plugins/varaverk/`. Never edited directly. Only updated via `git pull` (daily orchestrator or the pull button in the UI).
- **No Co-Authored-By** in commit messages unless explicitly asked.
- **No comments** unless the WHY is genuinely non-obvious.
- The `.plg` symlinks the installed plugin location directly to this workspace — one copy, no drift.
### Current workflow: edit here, push to Gitea
### Current workflow: dev/prod split
Pre-release — too many moving parts for a dev/prod split right now. Edits are made directly in `/boot/config/plugins/varaverk/` and pushed. This is intentional, not a gap.
Edit in dev, push to Gitea, pull prod when ready (daily orchestrator or manual UI trigger).
Push is the only bridge — no deploy hooks, no rsync-on-save, no direct path references between dev and prod.
### Future: dev/prod split (post-release)
When the codebase stabilises, the plan:
- **Dev** — a separate git clone somewhere on the array (`/mnt/user/Development/Varaverk/` or similar). All editing happens there.
- **Prod** — `/boot/config/plugins/varaverk/` remains as-is. Only updated via `git pull` (already handled by `git_pull_execute.sh` in the daily orchestrator, or triggered manually from the UI).
- **`plugin_setup.sh`** stays pointing at the prod path. Dev never touches `/boot/` directly.
- **Push is the only bridge** — no deploy hooks, no rsync-on-save, no direct path references between dev and prod. The old dev folder was deleted precisely because it violated this.
`plugin_setup.sh` stays pointing at the prod path. Dev never touches `/boot/` directly.
### Hard limits — do not cross these
- **Never create or modify `.claude/settings.json`** in this repo. No workspace hooks, ever. The stale hook that existed here previously fired `Deployment/deploy.sh` (now deleted) on every file edit and caused unintended deploys. If you think a hook would help, ask first.
- **Never change `HOST1_STORAGE_MODE_INTERNAL`** in `host1.conf`. Claude data belongs in `/mnt/user/appdata/claude-code/` — not inside this repo.
- **There is no dev folder.** The old `/mnt/user/Important Shit/Git/Development/Varaverk` copy was deleted. Do not recreate it.
- **Never move files between `Configurations/` and `Deployment/`** without explicit instruction. `Configurations/` = live runtime confs (gitignored). `Deployment/` = templates and setup tooling (tracked).
---