• 1 Post
  • 4 Comments
Joined 1Y ago
cake
Cake day: Jul 22, 2023

help-circle
rss

I didn’t read all the comments, so someone may have pointed this out already.

One of the main ideas is probably something like Fedora CoreOS, where the Quadlet systemd files are automatically created during first boot with something like Kickstart or cloud-init.

Instead of shipping the applications with the image, the OS image can be very minimal, while still being able to run very complex stuff.

When you add the fact that CoreOS and other atomic distros can update themselves in the background, and boot to an updated base image, the box just needs periodic reboots and everything stays updated and running with basically no interaction from the admin at all, best case.

Probably not so useful in the self-hosting / homelab context, but I can imagine the appeal on a larger scale.

I’ve been using Quadlet+Podman kube YAMLs for a while for my own self-hosted services, and it’s pretty rock solid. Currently experimenting with k3s, but I think I’ll soon switch back. Kubernetes is nice, but it’s a lot more fragile for just a single node. And there’s way too much I don’t understand…

I wrote a couple blog posts about the homelab setup, planning to add more when I have time. Give a read if you’re interested: https://oranki.net/tags/self-hosting-my-way/


In that case it’s definetly worth it to try this out, just so you have one more notification to disable


In that case hydroxide-push will work too, which is good news!

Just note that the IMAP, SMTP and CardDav functions have been stripped out from this push version. If there’s interest to have those too, a different version with the push stuff added on top of full Hydroxide could be made. It will require a bit of time to develop.

The scope of hydroxide-push is only push notifications for now.


I think it does require a paid account, Hydroxide basically acts like the official Proton bridge.

I haven’t actually tested with a free account, so there’s a chance it does work. When you run the auth command (which is the same as upstream Hydroxide), it will probably throw an error.

If you have a free account and try this out (or Hydroxide), please report how it goes back here, I’ll add a note to the readme. Upstream doesn’t seem to mention this in their repo either.


Ntfy.sh Protonmail notifications
cross-posted from: https://lemmy.world/post/17087912 >Protonmail relies solely on Firebase for receiving notifications on Android. While UniversalPush support is probably in the works, it may take some time until users on ROMs without GSF get built-in notifications. > > For those that already use ntfy.sh as a push provider for other apps, https://github.com/0ranki/hydroxide-push is a solution to get push notifications of new mail in Inbox. > > The service requires a Linux box to run on, and can be deployed as a container or by running the provided binary. Building from source is of course also an option. > > The service is a stripped down version of Hydroxide, the FOSS Protonmail Bridge alternative. There are no ports exposed, all communication is outwards. Communications to Proton servers use the Proton API. The service only receives events from Proton servers, and if the event is incoming mail, a notification is sent to a ntfy.sh server and topic of your choice. Other types of events are simply disregarded, and no other processing is done. The sent push event does not contain any detailed information. > > EDIT: Starting from version v0.28.8-push7 the daemon supports HTTP basic auth for the push endpoint. > > Disclaimer: I'm the author. All of the work is thanks to https://github.com/emersion/hydroxide, I've merely mutilized the great upstream project of most features for a single purpose. Issues, comments and pull requests are welcome!
fedilink
143
Ntfy.sh Protonmail notifications