51–60 of 68 posts
But the site was down ... and when I got home my cat was chewing on the ethernet wire.
So found some cheap virtual hosting that was much more stable.
Earlier quoted context omitted.
> Sorry, but we did all of that 20 years ago, and those approaches remain a lot simpler for basic use cases. Yeah, we did, and they were complicated then and they're complicated now. The difference is some of us have decades of experience which make them feel simpler. > And if you think that Kubernetes is always the right approach, then you clearly are NOT aware of the tradeoffs. I was very explicit that Kubernetes i…
Kubernetes wraps several layers of abstraction around the old way of doing things. There is no world in which the operation of the site is in any way clarified by involving Kubernetes. Kubernetes also adds performance overhead. There are things which are easier with Kubernetes. But only after you've climbed a long learning curve. From what I've seen, even people without "decades of experiment" find the non-abstracted…
Heh, I'm actually more interested in the "garage" piece of the blog which is barely touched on. I also run a home lab, but from my climate-controlled relatively clean basement. I've thought about moving it to the garage, but I'm worried about temperature and dust/dirt ingress. Do you have a sealed cabinet or air filters or any other environmental controls around the servers? Or are you using industrial machines rated…
I have seen production servers run for ten years upstairs a dirty bus repair shop. The room is never cleaned so there's a few millimeters of black dust on everything. In fact you know the age of a server depending on the amount of dust on it. There's a defective A/C unit that sometimes throw some water all around. There's power cut 2 or 3 times a year, the batteries are old so the servers get their hard reboot. As fa…
i have to clean my office setup every often and i use a blower to remove the dust. dust bunnies and all. still, everything works.
you are right, people often talk about hygiene for computers but they are more resilient than we are made to believe.
Earlier quoted context omitted.
(Author here) I mostly worry about security for this. If you have nothing private on your network it's probably fine, but if you have, say, a NAS that isn't using proper authentication (pretty common), an os/nginx vulnerability could end up exposing stuff. Of course there are much simpler ways to lock things down also :)
Then why are you intentionally adding another dozen attack surfaces and bleeding edge stuff constantly full of exploits? nginx remote exploits that matter are a once in a decade thing. Your setup is incomparably more insecure than nginx and a port forward. I've been running a static webserver from my home for more than 20 years now. By avoiding dynamic languages, databases, and buzzwords, I've never been hacked. Neve…
I used to run my own personal website out of my home. Until I went for a job interview and gave out a link to my website. But the site was down ... and when I got home my cat was chewing on the ethernet wire. So found some cheap virtual hosting that was much more stable.
This decision protects your home IP address, but it still makes you reliant on something that is not self-hosted. It kind of feels like cheating, but I can't think of a good way to mitigate. What happens if your home ISP gets DDOS'd? What's that like? How do you (or your ISP, or their ISP or ...someone) fix it?
>I self-host... and use Cloudflare Tunnel... This decision protects your home IP address, but it still makes you reliant on something that is not self-hosted. It kind of feels like cheating, but I can't think of a good way to mitigate. What happens if your home ISP gets DDOS'd? What's that like? How do you (or your ISP, or their ISP or ...someone) fix it?
>Well, hosting a blog from home is probably not a great idea from a practical perspective. I'm not a hater, but maybe he perceives it as not practical here because of all the fun unnecessary complexity. Keeping something like this going for more than a couple years would require complex sysadmin maintainence for updates (which is fun till it isn't). But if you just install nginx from your system repositories, have yo…
If all you're ever doing is hosting a static blog, then yeah, you don't need something like Kubernetes; however, if you want to host other services (e.g., database, authentication, comments, etc) then it quickly behooves you to build on some higher-level platform or else you'll end up building your own (poorly) and missing out on all of the experience, documentation, and tooling that are publicly available for Kubern…
After working with Docker and Kubernetes for some years, i consider that a huge win. Heck, even a cgi-bin script hacked together in perl is better documented and more reliable!
I used to run my own personal website out of my home. Until I went for a job interview and gave out a link to my website. But the site was down ... and when I got home my cat was chewing on the ethernet wire. So found some cheap virtual hosting that was much more stable.
Do you have suggestions for cheap hosting in Europe?
For network stability I'd prefer OVH, but they only offer you a single IPv6 address, which is just stupid - but depending on your use case that may not be so relevant to you. Hetzners VPS/cloud offering improved a lot in UX in recent year.
>I self-host... and use Cloudflare Tunnel... This decision protects your home IP address, but it still makes you reliant on something that is not self-hosted. It kind of feels like cheating, but I can't think of a good way to mitigate. What happens if your home ISP gets DDOS'd? What's that like? How do you (or your ISP, or their ISP or ...someone) fix it?
Perhaps having a setup where it has a fallback on Cloudflare Tunnel when you detect you're under a DDOS attack. Could this not be feasible?
2.) If your IP is under DDOS attack, you won't be able to connect to CF tunnel.