unraidclaw 0.1.12 → 0.1.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -71,6 +71,24 @@ With multi-server config, every tool accepts an optional `server` parameter (e.g
|
|
|
71
71
|
|
|
72
72
|
Set `tlsSkipVerify: true` when using UnraidClaw's auto-generated self-signed certificate.
|
|
73
73
|
|
|
74
|
+
### Keeping the API key out of the config file
|
|
75
|
+
|
|
76
|
+
You don't have to hard-code the key in `openclaw.json`. Two options:
|
|
77
|
+
|
|
78
|
+
**Environment variable** — OpenClaw expands `${VAR}` references at config-load time:
|
|
79
|
+
|
|
80
|
+
```json
|
|
81
|
+
"apiKey": "${UNRAID_API_KEY}"
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
**Provider-backed secret (`SecretRef`)** — point `apiKey` at one of your configured secret providers; OpenClaw resolves it before the plugin loads, so the plugin only ever sees the resolved string:
|
|
85
|
+
|
|
86
|
+
```json
|
|
87
|
+
"apiKey": { "source": "file", "provider": "default", "id": "/unraidclaw_key" }
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
`source` is one of `file`, `env`, or `exec`; `provider` names a provider from your `secrets.providers` config; `id` is the lookup key. Both forms also work per-server on `servers[].apiKey`. (Requires unraidclaw 0.1.12+.)
|
|
91
|
+
|
|
74
92
|
## Usage
|
|
75
93
|
|
|
76
94
|
Once installed and configured, just ask your agent:
|