mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1104] There is no Windows version to self-host ntfy #776
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#776
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JPMakesStuff on GitHub (May 6, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1104
It would seem the ntfy windows version is only for displaying notifications and not acting as a self-hosted server ???
Could a Windows server version which runs on a custom TCP port be released?
This would be very desirable for home automation setups where the less-than-stellar vendor only supports their own notification method but it's very slow or down most of the time.... Some example applications that run on Windows but notifications arrive too late or not at all: HomeSeer, NxWitness, Sighthound video, SyncBackSE
Yeah, I could run it in Docker, but ... why?
@binwiederhier commented on GitHub (May 8, 2024):
As of today, I have no desire to support the ntfy server on Windows. The client is relatively trivial, but for Windows, it'll likely require more work. If somebody put in the work to adjust and compile it for Windows, I'd likely be alright with it, but I won't put work into it.
@user8446 commented on GitHub (Jul 12, 2024):
Why not run it in WSL2? I run a Nextcloud server in WSL2 and it's just as stable as a standalone server.
@JPMakesStuff commented on GitHub (Aug 19, 2024):
Yeah, but then I'm having to run WSL also... I guess I'll take the hint dev dislikes Windows and I should go elsewhere, like Gotify or other suggestion?
@wtf911 commented on GitHub (May 5, 2025):
#1328
I've made it possible to compile the server for Windows. @binwiederhier kindly approve the pull request.
@wtf911 commented on GitHub (May 5, 2025):
ntfy.zip
For testing purposes here is the latest commit compiled for Windows with server working.
@sayyyed commented on GitHub (Jan 11, 2026):
thanks, i tried it and works very well, i am using it in production
@binwiederhier commented on GitHub (Jan 11, 2026):
Thanks for testing. I will review again what it takes to make the Windows version. Looks like it's already working without changes.
@binwiederhier commented on GitHub (Jan 11, 2026):
@wtf911 Is this still the only changes you had to make? https://github.com/binwiederhier/ntfy/pull/1328/changes
@wtf911 commented on GitHub (Jan 16, 2026):
@binwiederhier Yes, that's correct. That's all I did to be able to compile the Windows version and I added to be able to run it as a Windows service. Happy to see this getting some attention. :)
@binwiederhier commented on GitHub (Jan 18, 2026):
Done https://github.com/binwiederhier/ntfy/pull/1552 -- The next server release will contain a Windows server version. Tested on Win 11. Service is working too.