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

document current edit-and-push workflow and post-release dev/prod plan in CLAUDE.md

Browse Source
This commit is contained in:
Gmer4Lfe
2026-06-14 13:30:36 -04:00
parent 373388a77b
commit e8608a97b7
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+12
View File
@@ -7,6 +7,18 @@
- **No comments** unless the WHY is genuinely non-obvious. - **No comments** unless the WHY is genuinely non-obvious.
- The `.plg` symlinks the installed plugin location directly to this workspace — one copy, no drift. - The `.plg` symlinks the installed plugin location directly to this workspace — one copy, no drift.
### Current workflow: edit here, push to Gitea
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.
### 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.
### Hard limits — do not cross these ### 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 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.