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.

  • jokob@lemmy.worldOPEnglish
    1·
    10 months ago

    Hey, thanks for trying out NetAlertX.

    I’m using FF as my primary browser so not sure about why your experience is so different.

    I think I’ve done alright, writing an app that is configurable via json manifests, dynamically loaded settings and a plugin system everyone can contribute to.

    There are of course things to improve, and almost everything listed in your post is something on my long to-do list. It’s very easy to find flaws in things, but what’s more difficult is to contribute to the community and improve things.

    So if you are up for a challenge - open a PR and help me improve things step by step.

    Thanks in advance if you decide to help out! Otherwise, comments like these make free open-source work unenticing🙏

    EDIT: Fixed the empty settings (hopefully), added a remove last button on the subnets setting.

    Oh also - there is a well documented bulk-editing feature: https://github.com/jokob-sk/NetAlertX/blob/main/docs/DEVICES_BULK_EDITING.md VLANS are documented here: https://github.com/jokob-sk/NetAlertX/blob/main/docs/SUBNETS.md#vlan-example