lldap VS ntfy

Good to hear, I think it'll make many users happy. For me, I've migrated back to Authelia. I moved to authentik because at the time Authelia had no user management. After all of authentik's sharp edges, I've found lldap[0], and was able to implement a pilot in a few hours. I haven't looked back, since everything was converted.

[0]: https://github.com/lldap/lldap

I wrote LLDAP (https://github.com/lldap/lldap) after struggling to install and configure openLdap on my homelab.

I've recently installed and configured LLDAP (Lightweight LDAP) - More details here if you've never heard of it before: GitHub - lldap/lldap: Light LDAP implementation

I've an LLDAP instance running to make managing users easier.

I'm trying to integrate LDAP into my small homelab but I'm extreme noobie in it. So far I've tried: 1. OpenLDAP - not so resource heavy but I found it difficult go get working correctly with NextCloud, Keycloak and Jellyfin. Maybe someone could recommend an easy to follow guide? 2. LLDAP - honestly it's almost prefect. Nice clean UI, great guides how to setup with everything I need, but it's a read-only LDAP, so I cannot create or manage users with Keycloak or NC, that's about the only downside and probably bugs me more than it should. 3. 389ds - has everything I need (and probably some more), super easy to setup with this guide but the elephant in the room is that it uses 700MiB of RAM (whereas LLDAP uses only 7-8MiB). That's a big difference which really makes me question whether I want to use this particular solution.

Note that if you want to use KeyCloak for the OpenID but want to still have a LDAP source of truth, you can use LLDAP + KeyCloak together, with LLDAP as the source of truth and KeyCloak giving you the fancy features: https://github.com/lldap/lldap/blob/main/example_configs/key...

To be fair, their respective documentations (here and here) are pretty comprehensive.

Slightly related, but I've also been working on and off for a few years on my own Type 1 Diabetes management solution (https://github.com/algao1/iv3).

I haven't had time to work on it recently, but it uses ntfy (https://ntfy.sh/) to send alerts and such.

I was thinking of eventually incorporating some kind of automatic remedial solution eventually to help keep my glucose in range, but haven't had any time to look into it yet.

If you go to the settings, there should be a notification category, which then contains another menu "App Notifications" where you can see all the apps that are allowed to receive notifications, but I don't know if this will stop google play services to receive these identifiers.

I use GrapheneOS, so I don't have any google play services running, but for the apps where I need notifications I use https://unifiedpush.org/ (only a few apps implement it) and I host my own https://ntfy.sh server.

Kind of similar, in the early days of COVID, I accidentally discovered that my state's website would have test results available several hours before they sent out the "view your results" email. So I made a script that would check the site every five or ten minutes and then ping me as soon as the result changed to something besides PENDING.

In the course of that I stumbled on https://ntfy.sh/ which solved the notification problem without needing Twitter, and I've used it since then to let me know when long-running scripts complete.

I connect any app that supports https://unifiedpush.org/ to a self hosted https://ntfy.sh instance for fully self hosted push notifications

changedetection.io just donated to the awesome crew over at ntfy.sh

For further monitoring & alerting about critical cpu temperatures (unlikely now) for example, I plan to use notify & something else. Haven't thought about this much yet though.

I've started tossing https://ntfy.sh/ alerts into my Deno apps to get push notifications for things I'm interested in

ntfy.sh

If it was for fun and to learn how, that's fair. But are you aware of https://ntfy.sh?