Kenny_007

5 ms·

1.
by Kenny_007 7mo ago
Looks interesting. My homelab slowly turned into a mix of Portainer, btop and a couple of scripts as well. Some stuff runs on a small box at home, but I keep a few services on a tiny VPS cube-host) so they stay reachable if my home internet
2.
by Kenny_007 7mo ago
I ended up somewhere in the middle. A few things run on a small machine at home, but anything that needs to stay reachable lives on a cheap VPS. Mostly just a couple of docker containers and some basic monitoring.
3.
by Kenny_007 7mo ago
One thing that rarely shows up in these discussions is how uneven the data center world actually is. Hyperscale ai facilities and a typical colocation or regional cloud node don’t behave the same in terms of power, water or local impact, bu
4.
by Kenny_007 7mo ago
i’ve seen a few projects try to leave github completely and run everything self-hosted. the control is nice, but the contributor drop usually happens faster than expected. Most people won’t create another account just to open an issue or se
5.
by Kenny_007 7mo ago
Not necessarily. We’ve seen 403 spikes happen even when the edge was mostly fine but parts of the control plane were degraded. During incidents the dashboard, auth or analytics layers can fail independently from actual traffic handling. If
6.
by Kenny_007 7mo ago
For us the main shift was accepting that “being able to work locally” and “knowing whether users are affected” are two different problems. Local dev usually survives outages just fine. What hurts is losing external signals and assuming thin