• 1 Post
  • 334 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle

  • The purpose of the health check is to allow docker itself to talk to whatever service is running on the container to make sure it’s always responding happily, connected to everything it needs to be connected to for proper operation, and is not overloaded or stuck somehow.

    Docker does this by pretending to be a web browser, and going to the specified “health check URL”. The key thing I think you’re missing here is that the health check URL is supposed to be a URL that, ideally, runs on your container and does some meaningful checks on the health of your service, or at the very least, proves that when you connect to it, it is able to serve up a working static page or login page or something (which doesn’t actually prove it’s working completely, but is often good enough)

    Now, you’re probably wondering why this isn’t automatic, and the answer is because there’s no standard “health check URL” that fits all services. Not all services even respond to URLs at all, and the ones that do may have different URLs for their health checks, they may need different hostnames to be used, etc.

    By setting health check URL to example.com, basically what you’re doing is constantly testing whether the real-world website https://example.com/ way over there somewhere is working, and as long as it is, docker assumes your container is fine. Which it might be, or it might not be, it has no idea and you have no idea, because it’s not even attempting to connect to the container at all, it’s going to the URL you specified, which is way out there on the internet somewhere, and this effectively does nothing useful for you.

    It’s understandable why you probably thought this made sense, that it was testing network connectivity or something, but that is not the purpose of the health check URL, and if you don’t have a meaningful URL to check, you can probably just omit or disable the healthcheck in this case. Docker only uses it to decide if it needs to restart the container or alert you of the failure.



  • Avorion… like, don’t get me wrong, I’ve got 1,200+ hours in it, and on paper it still features literally everything that is like digital crack cocaine to me… but the updates and changes just keep going in directions that don’t interest me, at all, and even though they’re not explicitly bad per se, I find myself overwhelmed with disappointment about what the updates could’ve been, and I just become less interested, and end up playing less and less, to the point that I never even bothered installing it in 2025 and still don’t have it installed and when I do install it I generally just play it for a little bit and quickly become bored and disillusioned and end up going back to the X series or something to scratch the itch that it’s just not scratching for me anymore.



  • cecilkorik@lemmy.catoSelfhosted@lemmy.worldWhat else should I selfhost?
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    12 days ago

    Before you even start, consider adopting an ‘infrastructure as code’ approach. It will make your life a lot easier in the future.

    Start with any actual code: If you have any existing source code, get it under git version control immediately, then prioritize getting it into a git hub like forgejo to make your life easier in the future. Make a git repository for your infrastructure documentation, and record (and comment/document too if you’re feeling ambitious) every command you run in a txt file or an md file or a script, and do that as religiously as you can while you’re setting up all this self-hosted stuff. You may want to dig it up later to try and remember exactly what you did or in case stuff goes wrong and you need to back off and try again. It might seem pointless now, but a year from now, you’ll thank me.

    Especially prioritize getting your git stuff moved into a self-hosted forgejo if any of your stuff is hosted on the microsoft technoplague called github.


  • I ran Matrix for like a year, and pretty much hated every minute. It was fragile, complicated, and incredibly, bafflingly resource intensive. Matrix is an overengineered nightmare in my opinion, and it seems to be quickly distancing itself from self-hosters while pursuing enterprise usage. Neat technology, horrible implementation, misguided company.

    XMPP is a breath of fresh air in comparison. Just like we still use email everywhere (even for authentication nowadays, fun!), XMPP is not obsolete simply because it’s older. It’s a solid foundation, plenty extensible, and does almost everything I can imagine needing to do without unnecessary complexity.

    Matrix’s bridges are its killer feature, and it’s nice… when it works. But it’s simply not worth the headache of dealing with Matrix, in my opinion.


  • If the polls are rigged, does that imply that most Israelis don’t support the genocide? So … you think you’ve got a majority of people who don’t support the genocide and with that majority you plan to do … nothing? Just gonna … let the minority do what they want?

    There’s a word for that, the word is “support”. You might not think you’re supporting it, but if you’re not doing something to fight it, then yes, you are supporting it. Get to work. Nobody ever promised that doing the right thing has to be easy.



  • Lots of enabling in your comment.

    People like you, with no control over the big decisions. Just like Palestinians can’t control Hamas, Russians can’t control Putin, US citizens can’t control Trump, and so on.

    If people can’t control their own governments, who can? Who should? Other people’s governments? Is that how you think it’s supposed to work? That’s why Israel is obliterating Gaza? Because Gaza can’t get rid of Hamas themselves so Israel is going to do it for them? Do you think that is justified and the right way to do things? Is it Canada’s job to rescue the US? Is it Europe’s responsibility to stop Russia?

    Are Iranians responsible for the Iranian regime? Yes, they are, that’s why they’re fucking protesting and dying in the streets right now. Resist, fight back, don’t comply, undermine your illegitimate government until they can be toppled.

    Take responsibility. I am responsible for the actions of my government and my country. And so are you. You will be held responsible. And you should be. Other countries are not responsible for fixing your shit. You are. Fix it. Figure out how. Stop acting like it’s somebody else’s problem and you are just a humble peasant. Humble peasants can start revolutions. Lazy citizens who are happy with the status quo while pretending they don’t agree with it do not start revolutions. Which one are you?


  • I don’t want the free petition websites online getting my personal network’s info and sharing or selling it, hence the interest in self hosting.

    So either you’re creating a petition with a size of exactly “1” or you’re asking other people to trust YOU with their personal info instead, or you’re asking for a federated solution (extremely difficult to establish a verifiable web of trust framework, and STILL shares your “personal network’s info” whenever it federates or validates its data to dozens of other servers).

    None of these scenarios are viable for creating a petition that anyone is going to take seriously (to the extent that anyone takes petitions seriously at all)


  • fail2ban mainly, but also things like scaling login delays (some sort of option often built into the software you’re running, but just as often not configured by default), or if you’re feeling particularly paranoid account locking after too many failures, and in general just not using default, predictable, common usernames or weak passwords, and honestly it’s even helped a bit by having slow hardware and throttled network bandwidth.

    The goal is to make it so that someone can’t run a script that sends 100 million login attempts per second for common or stolen usernames and passwords and your server just helpfully tries them all and obediently tells them none of those worked… until one of them does.

    Not only does this encourage them to TRY sending 100 million login attempts per second because your server isn’t refusing it, which is a huge waste of bandwidth and resources, it also makes it really likely that they’re eventually going to guess one right.


  • It’s basically a free single-player demo with extra steps. Not being able to play on legitimate servers is realistically a huge drawback, honestly. And also, Microsoft knows it’s a huge opening for “piracy” which is why they’ve created Bedrock edition which is where all their monetization efforts and future content updates will be increasingly directed.

    Neither you nor I are supposed to ever care about Bedrock, or are ever expected to pay a cent for Minecraft. We are a tapped resource financially with nothing left to give and trying to get more money out of us and our community would be like trying to get blood from a stone. But that doesn’t mean we’re not important. Our role, even as free-to-play pirates in the Minecraft ecosystem, is to create content and create brand awareness, to keep it trending and on people’s radar, so that when children and whales are drawn to it, Microsoft makes sure the first thing they see is some Bedrock edition thing and they can start shelling out cash immediately.

    The whales, children, and naive parents are where the free money is. We’re just part of the advertising pipeline aimed at those demographics. We create buzz, they buy.


  • That’s the problem, When you’re running too many services as it is, you will be staring at a terminal at home sooner or later. Maybe you’ve gotten lucky and haven’t been ravaged by the cruel gods of fate yet, but it absolutely happens, and eventually it will happen to you. When you’re relying on family notifications and disaster response, you don’t get to choose when that happens, and sometimes you’ll have to spend a LONG time staring at a terminal at home. And when it happens often enough, or badly enough, you end up not just staring at the terminal at home, but also thinking about the terminal at home, and losing sleep over it, and that’s just not a great way to live your self-hosting life. I’ve been there.

    Making the investment in repeatable, reproducible, maintainable infrastructure now means you get to decide WHEN you’re staring at a terminal, and for exactly how long. Even when you don’t make it through as much progress as you wanted to, you can just close it down without any stress, get back to your life and continue from where you left off next time. You can’t do that, at least not without some significant consequences when your server got hacked and is sending spam or your entire server is refusing to boot and you need the files on it.

    You may still have to hit the terminal sometimes when you don’t choose to, but it’s going to be less often, and less complex when you do. That’s when the investment pays off, and your return on investment is the goal of having ultimately less time spent at the terminal at home, and that payoff is especially rewarding if you’re good at prioritizing the time you do choose to spend on the terminal at home, to find low-value moments to effectively repurpose for this hobby, and save the actually valuable times of your life from ever having to be used for emergency maintenance.



  • Speaking as a left-handed person it absolutely is a struggle, and given that the majority of the world is right-handed, for practical purposes it actually does need to be a struggle, otherwise ALL non-ambidextrous things would be a struggle for right-handed people instead, and that would be an even stupider way to run the world (as funny as it would be to see everybody else suddenly struggle with the things we struggle with on a daily basis, that’s not a fair or sensible way to expect any civilization to function)

    The things that left-handed people struggle with are due to subtle design issues caused by things that require asymmetric designs, you won’t notice an obvious problem with the asymmetry as a right-handed person, but they’re real struggles. Things like the shape being uncomfortable is only part of it, with scissors for example, the strength is coming from the wrong side, it won’t cut properly, for things like writing, our hands smear the ink as we go or have to be held hovering above leading to strain and poor penmanship, spines and bindings immediately get in our way the moment we start trying to write, many things don’t fit the way they’re supposed to, don’t have the correct angles when used in the left hand, or often they will block our vision or put our hand in a place that blocks our vision, whereas a right-handed person’s hand does not block their vision using the same tool. The issues are complex and subtle, but they’re significant, and they are not necessarily solved by simply making things symmetrical or reversing them. As much as lefties might enjoy a language that is written right-to-left, it’s not a practical solution to the reality that we are a minority where things are designed for the majority.

    Ironically the languages that DO write right-to-left, actually did not do it for the benefit of left-handed people, but did it to benefit right handed people, when they’re chiseling into stone tablets as the hammer (in their left hand) would block their view. So if you want to know how it feels to be left-handed, go chisel some essays on a stone tablet. It’ll make me feel better.


  • If you need low latency audio (ie, live music) Windows programs have to do a lot of ugly tricks to do this efficiently on Windows, and it’s different from the ugly tricks you have to do on Linux, and even if wine can attempt to translate the tricks from one to the other you may struggle trying to make this work well cross-platform to in Linux AFAIK.

    However if you’re just doing all-digital production I don’t see why wine wouldn’t work. Other people seem to have had success minus the latency issue I mentioned. And most of that was years ago, it mentions people are working on improving it, and honestly, Wine has come a really long way in the last 2 years. I’d recommend giving it a shot and see how it goes.


  • FWIW I don’t find Apache dated at all. It’s mature software, yes, but it’s also incredibly powerful and flexible, and regularly updated and improved. It’s probably not the fastest by any benchmark, but it was never intended to be (and for self-hosting, it doesn’t need to be). It’s an “everything and the kitchen sink” web server, and I don’t think that’s always the wrong choice. Personally, I find Apache’s litlte-known and perhaps misleadingly named Managed Domains (mod_md/MDomain) by far the easiest and clearest way to automatically manage and maintain SSL certificates, it’s really nice and worth looking into if you use Apache and are using any other solution for certificate renewal.