[PR #1399] [MERGED] Add Ntfy for Sandstorm to integrations.md #1593

New issue

Closed

opened 2026-05-07 01:02:49 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 01:02:49 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/binwiederhier/ntfy/pull/1399
Author: @orblivion
Created: 7/22/2025
Status: ✅ Merged
Merged: 8/8/2025
Merged by: @binwiederhier

Base: main ← Head: patch-1

📝 Commits (1)

4eb7dc5 Add Ntfy for Sandstorm to integrations.md

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 docs/integrations.md (+1 -0)

📄 Description

I packaged ntfy for Sandstorm, a self-hosting platform (similar to Yunohost, but more container based). Check out the link that I'm adding to see some details about my package. You can also run a demo of the app from there. It spins it up on the "alpha" server and deletes your account after some time.

Sandstorm is fairly opinionated, blocking unknown headers and also auth headers. So that precludes some of ntfy's features. I took out anything from the UI that rely on any of these, and also add a warning about it there to the user. Importantly, UnifiedPush works for me, as do my own json-based integrations in my personal scripts. I expect any integrations that don't rely on those headers to work. TBH probably most of my time was spent looking carefully into all of this.

I also added some onboarding text, since users may be coming from the Sandstorm app store, hearing about ntfy for the first time. I'd like to make it less "wall of text" and more streamlined and interactive in future versions. But I'm curious if something like this could be good for upstream as well?

The main benefit of choosing ntfy on Sandstorm is that it's really easy to spin up, and also to delete. And, it's conveniently alongside a growing list of other easy to install apps. Because Sandstorm is meant for "bite sized" apps owned by single users, I tell users to not share their ntfy instance with others. (other users can create their own). Users can create a new API URL for each integration, which makes it easy to revoke it later (not counting UnifiedPush, since that's tied to your phone). In the long run, I'd like to add some more features that you wouldn't want on a public server, like some sort of dashboard (if that runs too far away from your vision, I could change the branding. But I'd like it to work with the ntfy Android app.).

Over time I'd like to integrate it into Sandstorm more deeply. Sandstorm has something called the "powerbox" that lets you create interfaces between apps with CapnProto. It'll take some time to learn, but I'd love to make it so that we could create a package for (let's say) Changedetector.io, and allow the user to connect it to their ntfy instance with a few clicks instead of having to copy around API URLs.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/binwiederhier/ntfy/pull/1399 **Author:** [@orblivion](https://github.com/orblivion) **Created:** 7/22/2025 **Status:** ✅ Merged **Merged:** 8/8/2025 **Merged by:** [@binwiederhier](https://github.com/binwiederhier) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`4eb7dc5`](https://github.com/binwiederhier/ntfy/commit/4eb7dc563ccef18af40f6fc0d3ec6df8c93976b1) Add Ntfy for Sandstorm to integrations.md ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/integrations.md` (+1 -0) </details> ### 📄 Description I packaged ntfy for [Sandstorm](https://sandstorm.org), a self-hosting platform (similar to Yunohost, but more container based). Check out the link that I'm adding to see some details about my package. You can also run a demo of the app from there. It spins it up on the "alpha" server and deletes your account after some time. Sandstorm is fairly opinionated, blocking unknown headers and also auth headers. So that precludes some of ntfy's features. I took out anything from the UI that rely on any of these, and also add a warning about it there to the user. Importantly, UnifiedPush works for me, as do my own json-based integrations in my personal scripts. I expect any integrations that don't rely on those headers to work. TBH probably most of my time was spent looking carefully into all of this. I also added some onboarding text, since users may be coming from the Sandstorm app store, hearing about ntfy for the first time. I'd like to make it less "wall of text" and more streamlined and interactive in future versions. But I'm curious if something like this could be good for upstream as well? The main benefit of choosing ntfy on Sandstorm is that it's really easy to spin up, and also to delete. And, it's conveniently alongside a growing list of other easy to install apps. Because Sandstorm is meant for "bite sized" apps owned by single users, I tell users to not share their ntfy instance with others. (other users can create their own). Users can create a new API URL for each integration, which makes it easy to revoke it later (not counting UnifiedPush, since that's tied to your phone). In the long run, I'd like to add some more features that you wouldn't want on a public server, like some sort of dashboard (if that runs too far away from your vision, I could change the branding. But I'd like it to work with the ntfy Android app.). Over time I'd like to integrate it into Sandstorm more deeply. Sandstorm has something called the "powerbox" that lets you create interfaces between apps with CapnProto. It'll take some time to learn, but I'd love to make it so that we could create a package for (let's say) Changedetector.io, and allow the user to connect it to their ntfy instance with a few clicks instead of having to copy around API URLs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>