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:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Set of cron jobs that check services, then send a Matrix message if there's an issue.
For the cron jobs, I pipe stderr to another script that watches those and does the same.
If all fails, and internet is unavailable and the router crashes, a Pi will toggle a relay, cutting and resupplying power.
If Plex doesn’t add new shows/movies/music then I take a look at my services that should be adding stuff for Plex to serve up. That’s pretty much it these days. I had a few pinned tabs in my browser for some of them so can see if they aren’t working if I click on them to add/change something.
I was using homepage but it seems to cause docker to die a LOT on my server.
I mucked around with so many dashboards, homarr, homepage, dashy but settled on glance
Mainly because it's minimalist and mostly text based. Handles my RSS feeds and anything that I want render I can usually vibe using the custom API widget.
Uptime Kuma monitoring anything I care about and notifying me via Matrix, or notifying me via email if it's Matrix that's down.
i am un-admining. free-range artisanal services wherever i happen to drop them. hell i don't even know what's running and what's not until i try to access something.
i manage tech all day so my home tech is nothing but abject chaos and i'm ok with that. i have backups and i can go without if needed.
i am un-admining
Pretty much this. I just manually handle stuff when needed. I already work at IT so this feels quite liberating, the last thing I want is to annoy myself more, and the stuff I manage is not Critical™.
service still up = no problem
Can't access service = problem, better ssh in
Simple as
If a service falls in a server and no one is around to hear it, does it actually matter?
Great way to find services you really don’t need to be running.
Restart-always
Then avoid looking at your log files
Well yeah, it means the system can't keep torrentin' stuff!
ssh only after a reboot doesn't solve the problem, of course
Well, I saw in to reboot, so.
If something goes down my kids will be a more immediate and annoying alerting tool than anything I’ve used professionally.
Seconded..
I have just reduced the number of services to the couple I actually use, which I mostly remember exist. I have my own domain, so each service is service.mydomain.tld
Same for me. I use most of my services multiple times a week, so I find out pretty quickly if one isn’t working.
Same here 🙂 Last 3 times, things have broken because zfs raid on usb-connected DAS is not a great idea 😅😅
Even though Level1Tech said it works 😶🫣 https://youtu.be/GmQdlLCw-5k from 11:11 . Maybe terramaster use bad usb chipset.
I used a hodge-podge of chinesium parts and leftover drives to create a DAS system that hooks up to an HBA via DAC. I'm actually kinda surprised how stable it's all been.
I'm not, really. I run docker-compose and it runs. That's it.
I want to believe I’m a half step ahead with lazydocker
If I had time to make dashboards, I wouldn’t waste it making dashboards. Most of the stuff I have just works without a lot of attention, and that’s the way I like it.
I just wait for someone to scream if it breaks.
Unraid has a table of the docker containers.
I don't need metrics or stats. I wouldn't look at, or care about them anyway. Dashboards feel like tech enthusiast crap. Tech and resources for the sake of having tech. My services are to solve a problem, not look at metrics of.
Users, monitoring your services for free since internet exists
I just simply dont monitor most things. I do have a few things such as low disk space and failed backups. They are just simple shell scripts that send me an ntfy message when there is a problem.
I'll notice it's down when I try to access it and it doesn't work. If it's not down, there is nothing to manage 🙃
I have documentation if I need to see everything at a glance. I don't need a live-updating dashboard for that.
Does dockge count as a dashboard?
'Cause I use that to quickly check on what's running, what's stopped. Then I do most of my mainenance in a terminal, via SSH to the server.
I don't know how you guys function without some sort of visual. I will forget everything I'm running if it's not on a dashboard of some sort. That's not a maybe - it's guaranteed. Because it's happened before.
Surely, if you forget it's even running, you aren't using it, and it doesn't matter if it stops running? (With a couple of obvious exceptions like automated backups, etc)
It was often the automated things that I completely forgot about. I have ADHD, so if it's not accessible in a reasonable way (where I don't have to always google specific commands to find basic info on my own machine), then it gets lost in the memory hole. I know that a service is running, but would forget what it is.
These days I have it pretty down-pat. Hardware is labeled, static IPs are set for "critical" VMs and LXCs (because I'm shit at DNS and still trying to get that down), and things are actually somewhat documented in an easy-to-find place.
https://charity.wtf/2021/08/09/notes-on-the-perfidy-of-dashboards/
Graphs and stuff might be useful for doing capacity planning or observing some trends, but most likely you don't need either.
If you want to know when something is down (and you might not need to know), set up alerts. (And do it well, you should only receive "actionable" alerts. And after setting alerts, you should work on reducing how many actionable things you have to do.)
(I did set up Nagios to send graphs to Clickhouse, plotted by Grafana. But mostly because I wanted to learn a few things and... I was curious about network latencies and wanted to plan storage a bit long term. But I could live perfectly without those.)
I tried portainer for a while, but it was almost useless to me, as I'd always end up in the command line anyway. So I dropped that and any other dashboard idea.
Kubernetes with
I use portainer, not sure if that counts as a dashboard?
Bookmarks for linking to services. Grafana for graphs that I only look at if I am curious or looking into when a problem arises. I could use Uptime Kuma if I wanted a simpler solution or notifications.
I do have Dashboards in Grafana, but I only use them to look something up. I have Prometheus Alertmanager connected to a Matrix bot that sends me messages when something looks wrong.
Arch packages. All services have systemd integration.
https://github.com/nicolargo/glances
I have a dashboard as well (Homepage), but this is a nice look at system resource usage and what's running, at a glance.
Uptime-kuma emails me when services or critical LAN devices are unreachable for whatever reason.
I monitor everything with xymon, I get emails when there's a problem. Works like a charm.
docker stats
With that command, I get all the stats I need, no dashboard required.
FreshRSS to keep track of as much as possible, along with Uptime Kuma and plain old bookmarks
I use my own dashboard as a links page, nagios to monitor all the running servers and service's. Nagios will post to pushover if there's an issue.
docker ps
dokploy.com