bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Server stats:

250
active users

#sysadminlife

0 posts0 participants0 posts today

You know what's not normal at all?
I'm drinking a simple cup of coffee with this Chobani Dairy Coffee Creamer Caramel Macchiato, and the smell is simply overwhelming all around my house, like if I lighted up a scented candle. What in the world is in that thing? 🤔
#SysAdminLife #Coffee
chobani.com/products/creamers/

ChobaniCaramel Macchiato — Chobani® Coffee CreamerChobani® Coffee Creamer Caramel Macchiato. Real dairy. Crafted with clean, simple, only natural ingredients. Farm-fresh cream. Real milk. Real cane sugar.

Just read this from the status panel from one of my VPS providers:

“8th March 2025: 100.0000% uptime, 129 minutes maintenance”

The service was certainly down within that maintenance period.

Have I been doing my percentages wrong? If I brought something down for half an hour, that's ~2% of the day, so I would say uptime that day was 98%. Isn't it rather shady to say uptime was 100.0000% (six nines!), because all the downtime was during planned maintenance?

This morning, once again, I come across an interesting project. I head over to GitHub to take a look.

I read that the only supported way to use the project is via Docker because "providing installation instructions, given the underlying complexity, would be impossible." Not a fan of that, but okay, I start to understand… So, as I often do, I decide to open the Dockerfile (there’s no Compose). First line:

FROM alpine:3.14 AS base

No, your project isn’t "just" complex. It’s running on an outdated and potentially insecure base. And that’s a much bigger problem. It probably means it’s such a mess that updating it is impossible.

I close the GitHub page and move on with my life. 😆

Okay, that (kind of) settles it! 40% of the voters said I should keep writing about running things with Docker Compose in my blog, so that's what I'm gonna do.

However a close 36% said they also wanted me to add Podman + SystemD as an alternative. I will take feedback that into consideration, and think about how I can incorporate them, even if just a little bit (no promises though).

And what did I learn through the course of pondering/researching about this subject? Some people just want to use their home lab to self-host stuff, and learn about the stuff they host, not necessarily spend time or learn about the *infrastructure* behind the home lab, or the multiple ways to run it as similar as possible to a production environment (either with less/savaged hardware, or not caring about redundancy/HA).

Those were some very enlightening couple of days. Let's see how I can better make use of this research to tailor the way I share my experiences.

Thanks all who voted/commented! (and all the random posts I read to complement my data)

#HomeLab #SelfHosted #SysAdminLife #Forgejo

hachyderm.io/@badnetmask/11399

Hachyderm.ioMauricio Teixeira 🇧🇷🇺🇲 (@badnetmask@hachyderm.io)Poll: I've been reading some posts about people who converted their Docker Compose deployments to some sort of Kubernetes deployment (k3s, minikube or microk8s). Since I've been writing a lot of posts about self-hosting apps, I've been wondering about what people around here think would be better. #HomeLab #SelfHosted #SysAdminLife #Forgejo [ ] Keep writing about Docker Compose [ ] Migrate to some kind of mini-Kubernetes [ ] Add Podman + SystemD as an alternative [ ] Something else (please comment)

Poll: I've been reading some posts about people who converted their Docker Compose deployments to some sort of Kubernetes deployment (k3s, minikube or microk8s).

Since I've been writing a lot of posts about self-hosting apps, I've been wondering about what people around here think would be better.