You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open `http://localhost:3000` to view the dashboard! *(Requires Docker or Podman)*
68
+
Open `http://localhost:3000` to view the dashboard! *(Requires [Docker Desktop](https://www.docker.com/products/docker-desktop/)or Docker Engine)*
78
69
79
-
`compose.sh` auto-detects `docker compose`, `docker-compose`, `podman compose`, and `podman-compose`.
80
-
If both runtimes are installed, you can force Podman with `./compose.sh --engine podman up -d`.
81
-
Do not append a trailing `.` to that command; Compose treats it as a service name.
70
+
> **Podman users:** Replace `docker compose` with `podman compose`, or use the `compose.sh` wrapper which auto-detects your engine. Force Podman with `./compose.sh --engine podman up -d`.
82
71
83
72
---
84
73
85
74
## 🔄 **How to Update**
86
75
87
-
If you are coming from v0.9.5 or older, you must pull the new code and rebuild your containers to get the InfoNet testnet, Shodan integration, train tracking, 8 new intelligence layers, and all performance fixes in v0.9.6.
88
-
89
-
### 🐧 **Linux & 🍎 macOS** (Terminal / Zsh / Bash)
76
+
ShadowBroker uses pre-built Docker images — no local building required. Updating takes seconds:
90
77
91
-
Since these systems are Unix-based, you can use the helper script directly.
92
-
93
-
**Pull the latest code:**
94
-
```bash
95
-
git pull origin main
96
-
```
97
-
**Run the update script:**
98
78
```bash
99
-
./compose.sh down
100
-
./compose.sh up --build -d
79
+
docker compose pull
80
+
docker compose up -d
101
81
```
102
82
103
-
### 🪟 **Windows** (Command Prompt or PowerShell)
104
-
105
-
Windows handles scripts differently. You have two ways to update:
106
-
107
-
**Method A: The Direct Way (Recommended)**
108
-
Use the docker compose commands directly. This works in any Windows terminal (CMD, PowerShell, or Windows Terminal).
109
-
110
-
**Pull the latest code:**
111
-
```DOS
112
-
git pull origin main
113
-
```
83
+
That's it. `pull` grabs the latest images, `up -d` restarts the containers.
114
84
115
-
**Rebuild the containers:**
116
-
```DOS
117
-
docker compose down
118
-
docker compose up --build -d
119
-
```
120
-
121
-
**Method B: Using the Script (Git Bash)**
122
-
123
-
If you prefer using the ./compose.sh script on Windows, you must use Git Bash (installed with Git for Windows).
124
-
125
-
Open your project folder, Right-Click, and select "Open Git Bash here".
126
-
127
-
**Run the Linux commands:**
128
-
```bash
129
-
./compose.sh down
130
-
./compose.sh up --build -d
131
-
```
132
-
133
-
---
85
+
> **Coming from an older version?** Pull the latest repo code first, then pull images:
86
+
>
87
+
> ```bash
88
+
> git pull origin main
89
+
> docker compose down
90
+
> docker compose pull
91
+
> docker compose up -d
92
+
>```
134
93
135
94
### ⚠️ **Stuck on the old version?**
136
95
137
96
**If the dashboard still shows old data after updating:**
# Add your API keys in a repo-root .env file (optional — see Environment Variables below)
429
-
./compose.sh up -d
396
+
docker compose pull
397
+
docker compose up -d
430
398
```
431
399
432
400
Open `http://localhost:3000` to view the dashboard.
@@ -452,8 +420,7 @@ Open `http://localhost:3000` to view the dashboard.
452
420
># BACKEND_URL=http://myserver.com:9096
453
421
>```
454
422
455
-
If you prefer to call the container engine directly, Podman users can run `podman compose up -d`, or force the wrapper to use Podman with `./compose.sh --engine podman up -d`.
456
-
Depending on your local Podman configuration, `podman compose` may still delegate to an external compose provider while talking to the Podman socket.
423
+
**Podman users:** Replace `docker compose` with `podman compose`, or use the `compose.sh` wrapper which auto-detects your engine.
457
424
458
425
---
459
426
@@ -517,9 +484,8 @@ If you just want to run the dashboard without dealing with terminal commands:
517
484
518
485
Local launcher notes:
519
486
520
-
- `start.bat` / `start.sh` currently run the hardened web/local stack, not the final native desktop boundary.
521
-
- Security-sensitive paths are hardened up to the pre-Tauri boundary, but operator-facing responsiveness still matters and is part of the acceptance bar.
522
-
- If Wormhole identity or DM contact endpoints fail after an upgrade on Windows, see `F:\Codebase\Oracle\live-risk-dashboard\docs\mesh\pre-tauri-phase-closeout.md`for the secure-storage repair workflow.
487
+
- `start.bat` / `start.sh` run the app without Docker — they install dependencies and start both servers directly.
488
+
- If Wormhole identity or DM contact endpoints fail after an upgrade, check the `docs/mesh/` folder for troubleshooting.
0 commit comments