diff --git a/content/posts/easy-push-notifications-with-ntfy/index.md b/content/posts/easy-push-notifications-with-ntfy/index.md index 50f4b8f..d11b5a1 100644 --- a/content/posts/easy-push-notifications-with-ntfy/index.md +++ b/content/posts/easy-push-notifications-with-ntfy/index.md @@ -2,7 +2,6 @@ title: "Easy Push Notifications With ntfy.sh" date: 2023-09-17 # lastmod: 2023-09-17 -draft: true description: "Deploying and configuring a self-hosted pub-sub notification handler, getting another server to send a notifcation when it boots, and integrating the notification handler into Home Assistant." featured: false toc: true @@ -28,7 +27,7 @@ Wouldn't it be great if there was a simple way to send a notification to your ph I thought it sounded pretty compelling - and *then* I noticed that [ntfy's docs](https://docs.ntfy.sh/install/) made it sound really easy to self-host the server component, which would give me a bit more control and peace of mind. -{{% notice tip "Topics are public" %}} +{{% notice note "Topics are public" %}} Ntfy leverages uses a [pub-sub](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) approach, and (by default) all topics are public. This means that anyone can write to or read from any topic, which makes it important to use a topic name that others aren't likely to guess. Self-hosting lets you [define ACLs](https://docs.ntfy.sh/config/#access-control) to protect sensitive topics. diff --git a/layouts/partials/aside.html b/layouts/partials/aside.html index 61a306a..a896cde 100644 --- a/layouts/partials/aside.html +++ b/layouts/partials/aside.html @@ -5,27 +5,32 @@
{{ if .Params.date }}
posted: | {{ $postDate }} |
updated: | {{ $updateDate }} |
+
+