how did I NOT know about this?

About this video

The creator demonstrates ntfy (pronounced notify), a free, open-source push-notification tool you can self-host, as a way to get alerted when long command-line jobs finish instead of waiting at the terminal. He installs it with Docker — updating packages, installing docker.io, and running the container on port 80 — both on a cloud virtual machine and on a local Kali Linux machine, noting a Raspberry Pi would also work. He cites the cloud example he uses as $5 a month, with a $100 credit for 60 days for new users mentioned in the video. After installing the ntfy app on Android or iPhone and subscribing to a topic such as ‘coffee’, he sends alerts with a simple curl -d command addressed to server/topic. To make iPhone push work he edits /etc/ntfy/server.yml to set base-url and the upstream base URL to ntfy.sh, explaining that upstream only receives a message ID so iOS can pull the message from his own server. For a home server he adds a Cloudflare Tunnel so it is reachable remotely without opening ports. Examples include chaining commands with && for success and || for failure, piping an Nmap scan result into a notification, cron and Windows Task Scheduler jobs, delayed messages, a loop that alerts when a host comes back up, Uptime Kuma integration, and a PowerShell battery-level alert.

Key takeaways

• ntfy lets any command or script send a push notification to your phone with a single curl call to server/topic once you subscribe to that topic in the app.
• Self-hosting is a single Docker container; you can run it in the cloud for public access or at home and expose it safely with a Cloudflare Tunnel.
• iOS push requires setting base-url and upstream-base-url in server.yml; the upstream service only sees the message ID, not the notification content.
• Shell operators make alerts conditional: && notifies on success, || on failure, and using both gives different messages for up and down states.
• Beyond one-off jobs, ntfy fits cron jobs, scheduled tasks, monitoring tools like Uptime Kuma, scheduled/delayed messages, and scripts checking things like battery or CPU.

Episode details: published August 30, 2023 · 23:06 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: Do you STILL suck at subnetting?? (THE FINAL TEST) // EP 9 · Next: Hacking the world’s most popular database →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube