I just aim for “good enough”. Does it work, does it meet my needs? That’s good enough, even if it isn’t exactly the right way.
Like right now I have a system that needs manual intervention if I shut it down, or it’ll come back up non-functional. But it works well enough so I’ll just fix that eventually. I like to spend my free time doing more social or productive stuff.
I think a self-hosted platform as a service is just called a platform
If you want the next level up, set up a log collector like graylog or something.
Some do, but that means you’re locked in to whoever the landlord chooses for the ISP, and you can’t call the ISP for support if you have issues.
Why not a municipal service?
It’s open source, so you could always just patch it without paying too. But you should support the maintainers if you think they deserve it.
I have automatic updates through a watchtower fork, so I just leave it alone until it breaks, then I go to the project site to see what changed. This has happened maybe twice in the last couple years.
If both drives exhibit the behavior, I’d suspect the drive controller.
That’s the neat part, I don’t!
I have a docker-compose file, which is somewhat self-documenting, especially since I give everything descriptive names. Creds go in bitwarden anyway.
But then, my environment isn’t that complex, and I don’t have anything so custom that I need notes to replicate it.
Sounds like you should just explore TCP, IP, subnetting, routing, and DNS on their own, not necessarily from the perspective of self-hosting.
Sometimes the problem isn’t on your end. The server might be having issues, or your ISP. Have to rule those out too.
Either figure out a way to multi-cloud host, or just don’t use them, because they’re a single point of failure.
Just pop the heatsink off and do it.
Is it not exposed as an attribute of the container itself in the docker API?
172.16.0.0/12 has just over a million addresses. Less if you subnet it, obviously. What in the world are you doing that you’ve exhausted all of those?
I think Apache is overkill. Just use caddy or traefik if it’s containers. nginx if not.
I’d rather have a backup than a replica.
They’re not a company, FUTO is one rich guy.
A statement from cloudflare blamed “a spike in unusual traffic”, but I guess the actual cause of the outage was a config file generated in response exceeded the max size
https://www.cnbc.com/2025/11/18/cloudflare-down-outage-traffic-spike-x-chatgpt.html
Technically a DoS, but not in the most common sense
Well yes, you take the stairs to the next level.