diff --git a/docs/REVERSE_PROXY.md b/docs/REVERSE_PROXY.md index d655a7e6..018d9292 100755 --- a/docs/REVERSE_PROXY.md +++ b/docs/REVERSE_PROXY.md @@ -2,6 +2,10 @@ > Submitted by amazing [cvc90](https://github.com/cvc90) 🙏 + +> [!NOTE] +> There are 2 NGINX files for PiAlert, one for the bare-metal Debian install (`pialert.debian.conf`), and one for the docker container (`pialert.template.conf`). Both can be found in the [install](https://github.com/jokob-sk/Pi.Alert/tree/main/install) folder. Map, or use, the one appropriate for your setup. + ## NGINX HTTP Configuration (Direct Path) 1. On your NGINX server, create a new file called /etc/nginx/sites-available/pialert diff --git a/docs/SUBNETS.md b/docs/SUBNETS.md index f73c4a15..028b1045 100755 --- a/docs/SUBNETS.md +++ b/docs/SUBNETS.md @@ -2,6 +2,9 @@ You need to specify the network interface and the network mask. You can also configure multiple subnets and specify VLANS (see exceptions below). +> [!TIP] +> You may need to increase the time between scans `ARPSCAN_RUN_SCHD` and the timeout `ARPSCAN_RUN_TIMEOUT` settings when adding more subnets. If the timeout setting is exceeded, the scan is cancelled to prevent application hanging from rogue plugins. Check [debugging plugins](/docs/DEBUG_PLUGINS.md) for more tips. + ## Examples > [!NOTE] @@ -13,8 +16,6 @@ You need to specify the network interface and the network mask. You can also con * Two subnets: `SCAN_SUBNETS = ['192.168.1.0/24 --interface=eth0', '192.168.1.0/24 --interface=eth1 -vlan=107']` - - ## Explanation ### Network mask diff --git a/front/plugins/newdev_template/config.json b/front/plugins/newdev_template/config.json index f93bc6eb..cd224ef9 100755 --- a/front/plugins/newdev_template/config.json +++ b/front/plugins/newdev_template/config.json @@ -403,8 +403,7 @@ { "function": "dev_SkipRepeated", "type": "text.select", - "maxLength": 250, - "default_value": "", + "default_value": 0, "options": ["{value}"], "options_params" : [ {