A step-by-step guide to self-hosting the Gotify notification service using Docker and PostgreSQL.
@beeng@discuss.tchncs.de
link
fedilink
English
124d

What sort of notifications is this aimed at?

Magnus
creator
link
fedilink
English
224d

It’s got an open API so really there’s a lot more than my own use case.

I’m using it right now for getting notifications from flows in ActivePieces (I don’t want to get spammy with my site, which is the link in the original post, but there’s a how-to on getting that up and running also… ActivePieces is like a self-hosted Zapier)

@vividspecter@lemm.ee
link
fedilink
English
223d

I use it with apprise and mailrise (email interface over apprise) typically. Apprise is basically a generic notification sender that can send push notifications to a bunch of different clients, including gotify.

So, things like Proxmox errors get set to a fake mailrise address -> apprise -> gotify. And a lot of Linux apps in general (especially older ones) only support email notifications, so this is quite useful. You can also use apprise directly, even as a commandline interface. So you can make scripts to notify you of problems in cases where there isn’t already proper logging and notification support.

And I’ve setup diun to give me notifications for docker version updates. In this case, diun sends notifications to gotify directly.

For anything. You can get a push notification for anything you can make run a script or send an http request.

Synestine
link
fedilink
English
123d

It is designed for one user, multi-channel push notifications. Like Firebase Messaging but self-hosted. You can use Markdown when composing the messages and do about whatever you want.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 137 users / day
  • 560 users / week
  • 1.4K users / month
  • 3.89K users / 6 months
  • 1 subscriber
  • 4.17K Posts
  • 86.7K Comments
  • Modlog