I’m curious if/what others have found a solution to this problem;

I’ve been slowly switching most things to decentralised services, such as Piped/Invidious, LibreX search, even Lemmy to some degree. I also recently set up Dashy as a dashboard for my NAS.

Over the last few weeks, I’ve encountered many problems with the specific instances of these services that I’m using, and I frequently have to change instance. I’m not sure if others have this problem as well. Especially for LibreX, this is problematic because it’s not trivial to change the default search engine on Firefox desktop.

So I thought it would be nice to have a ‘status’ widget in Dashy showing the uptime/status of all of the specific instance servers I use — because sometimes it takes me a while to realise that actually the instance is down, not something else wrong with my network. But the only thing I could figure out how to do is simply put an iframe in Dashy with uptime websites such as https://gitetsu.github.io/librex-instances-upptime/. This is pretty clunky, and isn’t rendered nicely. An Invidious equivalent (https://stats.uptimerobot.com/89VnzSKAn) doesn’t allow iframes at all.

How do others deal with random instance downtime? Is there a better way of handling the outages in the first place? Is there a nice way of adding the instance status to my Dashboard so I at least know when they’re down?

Cheers.

@SheeEttin@lemmy.world
link
fedilink
English
11Y

I assume Dashy supports HTTP monitoring. Id just query the instance API or something.

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
  • 372 users / day
  • 584 users / week
  • 1.25K users / month
  • 3.86K users / 6 months
  • 1 subscriber
  • 3.73K Posts
  • 75.4K Comments
  • Modlog