Scrub remaining Claude references from docs

This commit is contained in:
Gmer4Lfe
2026-07-03 08:25:09 -04:00
parent 5d5b60a8ed
commit 14ecf0c08a
6 changed files with 1 additions and 48 deletions
-36
View File
@@ -21,7 +21,6 @@ making any changes.
- [smart_long_test.sh](#smart_long_testsh)
- [arr_profile_enforcer.sh](#arr_profile_enforcersh)
- [webhook_setup.sh](#webhook_setupsh)
- [claude_startup.sh](#claude_startupsh)
- [ramdisk_stop.sh](#ramdisk_stopsh)
- [Adding a New Tool](#adding-a-new-tool)
@@ -666,41 +665,6 @@ webhook_setup.sh --dry-run
---
## claude_startup.sh
Restores Claude Code's persistent data after an unRAID reboot and optionally launches
Claude. Standalone script — no common.sh dependency.
### Why This Exists
unRAID's root filesystem lives in RAM — `/root/.claude` and `/root/.local` are wiped on
every reboot. This script symlinks both directories back to persistent appdata storage
at `/mnt/user/appdata/claude-code/` before launching Claude.
### First Run Migration
On first run, if persistent storage is empty, the script migrates from current live locations:
```
/root/.claude → /mnt/user/appdata/claude-code/.claude
/root/.local/share/claude → /mnt/user/appdata/claude-code/local/share/claude
```
Subsequent runs skip the migration and only create the symlinks.
### Calling from array_started.sh
`array_started.sh` calls `claude_startup.sh` directly (no flags). This sets up the
symlinks only — no interactive session is launched. That is the default behavior.
### Usage
```bash
claude_startup.sh # set up persistent symlinks only (default — used by array_started.sh)
claude_startup.sh --launch # set up symlinks and launch Claude interactively
```
---
## ramdisk_stop.sh