cool. can you give me some examples of how one might use this?
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Yeah Iβm looking for some practical examples too
Yeah Iβm looking for some practical examples too
It's a nice way to send notifications to your phone about all sorts of things. Due to the fact that it just needs a simple curl command to trigger a notification, it's incredibly flexible.
Haven't used ntfy, but since it's fairly similar to gotify, which I have run for a while, these might give you an idea:
- uptime monitoring service like uptime kuma, so I get a notification to my phone when a service or server goes down
- sonarr/radarr to notify me when a new episode of a TV show or movie gets grabbed
- monitoring script that kept an eye on my disk-space on a fairly small VPS
- octoprint to send low-priority notifications when a 3D print is finished and high-priority notifications when a print failed
Basically, if you have any services/scripts that just run silently in the background and do their thing, but you want to be notified when something specific happens, applications like ntfy or gotify come in pretty handy. And since all you need to trigger a notification is a simple curl command, it's easy to integrate with all sorts of stuff.
//edit: their website also has a list of integrations which might give you some ideas: https://docs.ntfy.sh/integrations/
I have a backup script that runs every morning and I had it send a notification with ntfy on how many errors/warnings occurred. With backups it's important to actually know your backups are working.
I also have it report battery voltage and health every so often, which should hopefully give me advance warning of a spicy pillow in my laptop server.
Vikunja is a todo-app I enjoy quite a bit, but it only has email notifications. I made a script that runs every 15 minutes that reads all the tasks from the Vikunja API and sends me reminders or overdue tasks, and ntfy allows me to configure buttons on the notification which allows me to mark things done without having to open Vikunja.
It's a pretty good tool for anywhere you would want notifications.
How would the PWA be any better than the actual native iOS app?
The biggest reason is that PWA allows for web push notifications.
iOS is pretty strict when it comes to background apps keeping open connections, that's one of the reasons why there is no gotify app on iOS. They list the possible workaround with apple's APN service, but that would kind of defeat the purpose of selfhosting,
I'm afraid the biggest obstacle would be Apple's strict restrictions on background services. We cannot keep a persistent WebSocket connection in the background without abusing some APIs, which will absolutely disqualify the app from going onto the App Store and drain the battery significantly. Notifications could only be delivered through APN, which requires a developer account and a central server to manage notifications and send them to Apple before reaching the user, but this is not what gotify is designed for.
https://github.com/gotify/server/issues/87#issuecomment-457453135
//edit: If you check the ntfy docs, you'll see that instant delivery is not supported on iOS. So if you have uses that are time-sensitive, PWA with web push definitely has the advantage.
Iβm a big fan of nfty and Iβm looking forward to the improved PWA so that my iOS experience is just that much better. Thanks for all your efforts!
How is the battery life with PWA? I want to make sure the web socket connection doesnβt noticeably drain my phoneβs battery.
Is there plans to add integrations to other self host apps? I could see it being useful for integrations with Lemmy and arr software specifically. Doing this would increase popularity with it since it increases use cases.
It's already integrated into a bunch of things, especially the *arrs, but if you have suggestions, please let me or the maintainers of the other software know.
Here's a list: https://docs.ntfy.sh/integrations/
Oh that's nice I'll have to look into adding this then. Thanks!
Hey I looked into this some more, and.had a question. If I locked the web part behind my own auth provider and keep API part open but not exposed externally, would that be the way to keep publishing and subscribing private? I'd plan on using PWA, so breaking app versions wouldn't be a concern.
Just try it out. I make no guarantees for odd setups like that though. :-)
Is this intended as an alternative to pushover?