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.
The practice of calling a product “FooBar X”, unless it’s literally your version 10 that you just happen to be marketing in Roman numerals, feels a bit like those businesses that named themselves “Plumbing 2000”, it’s a bit tacky and doesn’t tend to age well IMHO. But hey, it’s not like it’d be the first software with a slightly kitsch name I use either lol
I was thinking about that sooo much, but difficult to find a free domain for networking-related projects. I think I delayed the rename by a month because I couldn’t decide. So yeah, I am not the happiest about the X at the end myself, but I also don’t have that much money to get a proper domain, so NetAlertX it is :)
Naming is really hard, I can’t blame you haha. I never had to name public facing things, at work I usually advocate for either really straightforward descriptive names or just having fun on a theme (e.g. we had classical music based stuff at one place, like Orchestra, Sonata, Symphony, and pop culture/nerdy stuff at another like Marvel heroes or SW characters, etc). Coming up with a name that’s marketable, discoverable and searchable sounds like a nightmare lol