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
Copy file name to clipboardExpand all lines: README.md
+6-20Lines changed: 6 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,11 +53,8 @@ Since then, it has continued to evolve and has been exhibited at major cybersecu
53
53
git clone https://github.com/DistriNet/BugHog
54
54
cd BugHog
55
55
56
-
# Pull the pre-built Docker images from Docker Hub
57
-
./scripts/pull.sh
58
-
59
-
# Start BugHog
60
-
./scripts/start.sh
56
+
# Pull the latest pre-built images from Docker Hub and start BugHog
57
+
./scripts/deploy.sh
61
58
```
62
59
63
60
Open your web browser and navigate to [http://localhost:80](http://localhost:80) to access the graphical user interface.
@@ -72,7 +69,7 @@ If BugHog is started on a remote server, substitute 'localhost' with the appropr
72
69
> [!TIP]
73
70
> Our [30-minute tutorial](https://github.com/DistriNet/BugHog/wiki/Tutorial) will guide you on how to use BugHog to trace a real bug's lifecycle!
74
71
75
-
To stop BugHog, simply run this in the project root:
72
+
To stop BugHog (including any running worker containers), run this in the project root:
76
73
77
74
```bash
78
75
./scripts/stop.sh
@@ -81,28 +78,17 @@ To stop BugHog, simply run this in the project root:
81
78
82
79
## Development :hammer_and_wrench:
83
80
84
-
Use the following commands to build the Docker images yourself, for instance after you made changes to the source code:
81
+
Use the following command to build all Docker images from the current codebase and start BugHog, for instance after you made changes to the source code:
85
82
86
83
```bash
87
-
# Build BugHog images
88
-
./scripts/build.sh
89
-
90
-
# Run the freshly built images
91
-
./scripts/start.sh
84
+
./scripts/build-deploy.sh
92
85
```
93
86
94
-
> [!NOTE]
95
-
> For reference, building takes about 4 minutes on a machine with 8 CPU cores and 8 GB of RAM.
87
+
This builds all images (core, nginx, and all subject workers) tagged as `dev`.
96
88
97
89
98
90
### Debugging
99
91
100
-
The most convenient debugging approach is to launch an interactive Node environment.
101
-
The UI can be visited at [http://localhost:5173](http://localhost:5173).
102
-
103
-
```bash
104
-
./scripts/node_dev.sh
105
-
```
106
92
107
93
For debugging the core application, consider using the VS Code dev container.
108
94
You can utilize the configuration in [.devcontainer](.devcontainer) for this.
0 commit comments