brum 1.6.1

Multi-Pane Web Environment (File Commander/Manager) - By Woofson
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158

# Commander Fleet: Testing & Verification Guide

Welcome to the **Commander Fleet** verification walkthrough. This step-by-step guide will walk you through testing multi-node orchestration, cross-pane remote file management, and streamed cross-node transfers in Brum.

---

## Step 0: Architecture Overview

Commander Fleet allows each browser panel to independently bind to different Brum nodes across your network, VPN, or local ports:
* **Node A (Host 1)**: e.g. `http://localhost:3140`
* **Node B (Host 2 / Test Node)**: e.g. `http://localhost:3141` or a remote machine (`http://nas.local:3140`, `http://100.x.y.z:3140`)

---

## Step 1: Spin Up a Secondary Test Node

If you already have a second Brum server running on your network/VPN, you can skip to **Step 2**.

To spin up a secondary test node locally on port `3141`:

```bash
# In a new terminal window:
PORT=3141 STORAGE_BASE_DIR=/tmp/fleet-test-node cargo run
```

---

## Step 2: Generate an API Token on Node 2

1. Open Node 2 in your browser: `http://localhost:3141` (or your remote host).
2. Open **Settings** (<kbd>F10</kbd>).
3. Click the **Security & Access** tab, then click **API Tokens & Service Credentials**.
4. Click **+ New API Token**:
   - **Token Name**: `Fleet Primary Console`
   - **Role**: `Admin` (or Read/Write)
   - **Expiration**: `Never (Persistent)`
5. Copy the generated token string (`arf_...`).

---

## Step 3: Register Node 2 in Fleet Manager on Node 1

1. Return to your primary Brum session: `http://localhost:3140`.
2. Open the **Tools Launchpad** $\rightarrow$ select **Fleet Manager** (or click the Server badge in the top header $\rightarrow$ **Fleet Manager**).
3. Under **Add Remote Node Profile**, fill in:
   - **Node Name**: `Secondary Test Node` (or `Goshawk NAS`)
   - **Endpoint URL**: `http://localhost:3141` (or `http://remote-ip:3140`)
   - **Accent Color**: Pick an accent color (e.g. Amber `#f59e0b` or Cyan `#06b6d4`)
   - **Auth Token**: Paste the `arf_...` token from Step 2.
4. Click **Add Node**.
5. Verify the node appears in the saved list with a green ping status indicator.

---

## Step 4: Cross-Pane Multi-Node Binding (The Dual-Panel Power Move)

1. Look at the pane sub-headers:
   - **Panel 1 (Left)**: Shows `Localhost` with a green indicator.
   - **Panel 2 (Right)**: Shows `Localhost` with a green indicator.
2. Click the `Localhost` button on **Panel 2 (Right)** header.
3. Select **`Secondary Test Node`** from the dropdown.
4. **Verification**:
   - Panel 2 now illuminates with the remote node's accent glow.
   - Panel 2 breadcrumb bar shows the `[Secondary Test Node]` badge chip.
   - Directory contents in Panel 2 now represent Node 2's filesystem!

---

## Step 5: Test Remote VFS Navigation & Root Switching

1. In Panel 2 (Remote), click the root dropdown (`/` icon) on the breadcrumb bar:
   - Notice that available roots (Storage base, Home, Disks) reflect Node 2's drives and configuration.
2. Double-click folders to navigate into remote directories.
3. Press <kbd>F7</kbd> (or click `+ New Folder`) in Panel 2:
   - Create folder `fleet-transfer-test`.
   - Verify it appears instantly on the remote node.

---

## Step 6: Test Cross-Node Streamed Transfers (F5 Copy & F6 Move)

1. In **Panel 1 (Local)**, select one or more files (e.g. text files, images, or audio tracks).
2. Press **`F5`** (Copy):
   - Notice the copy dialog indicates source and destination targets across different nodes.
   - Confirm copy.
3. **Verification**:
   - The Task Manager pill in the bottom status bar tracks the streamed pipeline transfer (`Source Node` $\rightarrow$ `Browser Stream` $\rightarrow$ `Destination Node`).
   - The files appear in Panel 2 (Remote) once complete.
4. Try transferring in the opposite direction (Panel 2 Remote $\rightarrow$ Panel 1 Local).
5. Try **`F6`** (Move) to verify source deletion upon successful transfer.

---

## Step 7: Test Remote Viewers, Code Editor & Media Streaming

1. **Document Viewer (`F3` / Click)**:
   - Click a `.md`, `.txt`, or `.log` file in Panel 2 (Remote).
   - Verify the document viewer opens, displays the remote content, and dynamic tools (`tail -f`, line numbers, wrap) work seamlessly.
2. **Code Editor (`F4`)**:
   - Select a remote file in Panel 2 and press <kbd>F4</kbd>.
   - Make an edit and press <kbd>Ctrl+S</kbd>.
   - Verify the file is saved directly to the remote node.
3. **Audio Streaming**:
   - Double click an `.mp3` or `.flac` file in Panel 2 (Remote).
   - Verify Audio Player streams audio smoothly from the remote host with seeking and ID3 tags.
4. **Video Player**:
   - Click a `.mp4` or `.mkv` file on the remote pane and verify HTTP range-request seekable streaming.

---

---

## Step 9: Test Gateway Hub Reverse Proxy & Terminal WebSocket Tunneling

When connecting to your primary Brum console from an HTTPS domain, remote LAN/WAN nodes can be transparently reverse-proxied through the primary host without mixed-content blocks:

1. **Gateway Proxy Routing**:
   - Open **Fleet Manager** and edit the remote node profile.
   - Set **Proxy Mode** to **`Gateway Proxy (Route via Gateway Hub)`** (or leave as `Auto`).
   - Click **Save Node Profile**.
   - Notice the blue `[Gateway]` pill badge appears on the node card.
2. **Gateway Health Probe**:
   - Click **Test Connection** in the node editor.
   - Verify it tests via `/api/fleet/ping/probe` through the Gateway Hub with round-trip latency and remote host status reported.
3. **Remote Terminal WebSocket Tunneling**:
   - Bind Panel 2 to the remote node.
   - Press <kbd>\`</kbd> (Backtick) or click **Terminal** on Panel 2's header.
   - Verify that Bite! Terminal connects to the remote host's shell via the gateway WebSocket tunnel (`/api/fleet/proxy/<node_id>/api/terminal/ws`).
   - Run commands (`uname -a`, `hostname`, `ls`) and verify they execute on the remote node.
4. **End-to-End SHA-256 Verification**:
   - Transfer a file from Panel 1 to Panel 2 (<kbd>F5</kbd>).
   - Check the Task card and ensure `SHA-256 Match: <hash>` confirms cryptographic integrity between source and target nodes.

---

## Step 10: Test Disconnect & Quick Switching

1. On Panel 2 (Remote), click the small **`✕`** icon on the `[Secondary Test Node]` breadcrumb badge (or click the node button $\rightarrow$ select `Localhost`).
2. Verify Panel 2 smoothly switches back to Localhost and restores your previous local directory.

---

## Verification Checklist

| Test Item | Status | Notes |
| :--- | :---: | :--- |
| Node registration in Fleet Manager | [ ] | Ping test green |
| Gateway Hub Proxy mode & blue badge | [ ] | `/api/fleet/proxy/<node-id>` active |
| Pane 2 switched to remote node | [ ] | Breadcrumb chip & glow visible |
| Remote directory listing & navigation | [ ] | Subfolders load properly |
| Remote folder creation (<kbd>F7</kbd>) | [ ] | Created on target node |
| Cross-pane file copy (<kbd>F5</kbd>) with SHA-256 | [ ] | Local $\rightarrow$ Remote streamed with hash match |
| Cross-pane file move (<kbd>F6</kbd>) | [ ] | Remote $\rightarrow$ Local streamed |
| Remote file viewing (<kbd>F3</kbd>) & editing (<kbd>F4</kbd>) | [ ] | Direct save confirmed |
| Remote terminal WebSocket tunneling | [ ] | PTY connected via Gateway proxy WS |
| Audio streaming from remote node | [ ] | Audio plays with seek bar |
| Pane 1-click disconnect | [ ] | Returns to Localhost |