Replies: 1 comment 1 reply
-
Hi, You don't need to map any plugins in the What you have to map and backup, are the Hope this makes sense, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
new to docker and NetAlertX, recently installed both.
NetAlertX is installed in /opt/stacks/netalertx
here is compose.yaml file:
services:
netalertx:
container_name: netalertx
image: "jokobsk/netalertx:latest"
network_mode: "host"
restart: unless-stopped
volumes:
- ./data/config:/app/config
- ./data/db:/app/db
- ./data/logs:/app/front/log
environment:
- TZ="America/Los_Angeles"
- PORT=20211
i noticed in /opt/stacks/netalertx/data/config/app.conf that paths for the plugins are entered like this: ...
ARPSCAN
#---------------------------
ARPSCAN_CMD='python3 /app/front/plugins/arp_scan/script.py userSubnets={subnets}'
AVAHISCAN
#---------------------------
AVAHISCAN_CMD='python3 /app/front/plugins/avahi_scan/avahi_scan.py'
... so the mapping of dir/files in the compose.yaml ensures the plugins can be executed, yes? my devices are being discovered but wanted to verify.
Beta Was this translation helpful? Give feedback.
All reactions