Gotify – a self-hosted push-notifications service
1–10 of 100 posts
Re: Gotify – a self-hosted push-notifications service
#2Re: Gotify – a self-hosted push-notifications service
#3Interesting project. Is this intended to replace Firebase Cloud Messaging on android or be a wrapper in front of it?
I only saw android support, anything for iOS in the works?
Re: Gotify – a self-hosted push-notifications service
#4I gave it a quick try and "it just worked" with minimal configuration. Really easy to get started.
Unfortunately messages are only plaintext.
Re: Gotify – a self-hosted push-notifications service
#5I gave it a quick try and "it just worked" with minimal configuration. Really easy to get started. Unfortunately messages are only plaintext.
Use JSON
Re: Gotify – a self-hosted push-notifications service
#6I gave it a quick try and "it just worked" with minimal configuration. Really easy to get started. Unfortunately messages are only plaintext.
Same. I wasted more time this evening setting up octobercms behind a reverse proxy (hours, not working) than getting that server handling notifications from a VPS running many small services.
Re: Gotify – a self-hosted push-notifications service
#7Logo reminds me of traefik. Is it related ?
Re: Gotify – a self-hosted push-notifications service
#8Off-topic
I got so scared when I looked at the swagger. The authentication uses the exact same variables as mine and is somewhat similar. The name of the endpoints are also very similar and the project has resemblance to mine.
That was really really akward for a moment.
I'll use the project though ( different use-case), looks really interesting. Coincidentally it's for the same project as I mentioned.
Re: Gotify – a self-hosted push-notifications service
#9Interesting project. Is this intended to replace Firebase Cloud Messaging on android or be a wrapper in front of it? I only saw android support, anything for iOS in the works?
From what I can tell it appears to be a replacement FCM/APNS. The client subscribes directly via websocket to a self-hosted server (Go binary).
New messages in the queue are then notified (gotified) via the websocket. https://gotify.net/api-docs#/message/streamMessages
The payload can be picked up and managed via REST API as well.
I'm building a similar solution for a slightly different usecase, so wanted to have a look under the hood. There's nothing I can see that would stop you using this for iOS so maybe they just don't have a iOS dev on the project.
Edit: Ah, here's why. https://github.com/gotify/server/issues/87
Re: Gotify – a self-hosted push-notifications service
#10It is worth noting that this will use a noticeable amount of power more than Google cloud messaging. The basic idea of how is works is about the same, but the devil is in the details. If you look at an idle connection over LTE, you will notice that after a while your carrier will close it. You need keepalives. If you look at the connection for Google cloud messaging, you might notice that it needs much fewer keep alives than YOU need to keep your connection alive. This means fewer wakes from sleep mode and lower power.