Session log: GuruRMM audit, installer system, infrastructure fixes
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -4,6 +4,9 @@
|
||||
**Status:** [OK] Complete - Production Ready
|
||||
**Author:** Coding Agent (Claude Sonnet 4.5)
|
||||
|
||||
**Source Repo:** `azcomputerguru/gururmm` on git.azcomputerguru.com (active development, 53+ commits).
|
||||
Note: A `guru-rmm` repo also exists but is a restructured copy with only 2 commits -- use `gururmm` as the primary reference.
|
||||
|
||||
---
|
||||
|
||||
## What Was Built
|
||||
@@ -187,6 +190,10 @@ once_cell = "1.19"
|
||||
|
||||
Follow instructions in `commands_modifications.rs`:
|
||||
|
||||
> **Note:** `claude_task` is a NEW command type added by this integration. The existing
|
||||
> GuruRMM command types are: `shell`, `powershell`, `python`, `script`. This step adds
|
||||
> `claude_task` as an additional type in the command dispatcher.
|
||||
|
||||
1. Add module declaration: `mod claude;`
|
||||
2. Add imports: `use crate::claude::{ClaudeExecutor, ClaudeTaskCommand};`
|
||||
3. Create global executor: `static CLAUDE_EXECUTOR: Lazy<ClaudeExecutor> = ...`
|
||||
@@ -243,7 +250,9 @@ Follow deployment process in `TESTING_AND_DEPLOYMENT.md`:
|
||||
|
||||
## Usage Example
|
||||
|
||||
Once deployed, Main Claude can invoke tasks on AD2:
|
||||
Once deployed, Main Claude can invoke tasks on AD2. The curl command below creates the
|
||||
command on the server via REST; the server then delivers it to the agent over WebSocket
|
||||
(ServerMessage::Command):
|
||||
|
||||
```bash
|
||||
curl -X POST "http://172.16.3.30:3001/api/agents/{AD2_AGENT_ID}/command" \
|
||||
@@ -394,7 +403,7 @@ A: Check agent logs at `C:\Program Files\GuruRMM\logs\agent.log` for detailed er
|
||||
1. **TESTING_AND_DEPLOYMENT.md** - Complete testing and troubleshooting guide
|
||||
2. **README.md** - Full project documentation with examples
|
||||
3. **Agent logs** - `C:\Program Files\GuruRMM\logs\agent.log`
|
||||
4. **GuruRMM server logs** - `http://172.16.3.30:3001/logs`
|
||||
4. **GuruRMM server logs** - Check server-side logs on disk (no `/logs` HTTP endpoint exists)
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user