After thinking for about a year about it I decided to rename the project to ๐NetAlertX. This will help prevent confusion about which fork someone is using, and differentiate it from the now stale upstream project. With about 1800 or so commits over the stale project, I thought, this project deserved a new name. It will also remove the confusion about only supporting Raspberry Pi's ๐ต
On top of the rename, I implemented โจunlimited icons - just find an SVG you like and use it ๐.
The rename from PiAlert to NetAlertX should be pretty straightforward and existing setups should work fine, no manual migration steps should be necessary. Still, caution is recommended.
Check this https://github.com/jokob-sk/NetAlertX/issues/633 thread for edge-cases and the guide https://github.com/jokob-sk/NetAlertX/blob/main/docs/MIGRATION.md if you decide to change your docker-compose.
This is awesome. Will it work with VLANs or would I need an instance for each VLAN? I can do either, but allowing for VLANs would be awesome.
VLANS are supported - check out the docs ๐: https://github.com/jokob-sk/NetAlertX/blob/main/docs/SUBNETS.md#vlan-example
Oh, I you just made me very happy. New toy, which will make my wife somewhat unhappy ๐คฃ. Thanks so much.
And of course I'm going to RTFM, really appreciate the direct link. I just play with so much stuff already that I prefer to ask some key questions before I jump into a rabbit hole.