Canadian software engineer living in Europe.

  • 5 Posts
  • 183 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle

  • I’ve been using Linux for 25 years. I started with SuSe, switched to RedHat after a couple months, and after a few more months switched to Gentoo… for 10 years, then did Arch for the remainder.

    Frankly, I think that distro hopping is a bad idea because it means you don’t get enough time really understanding how to fix things. As a long time Arch user, it would never occur to me to throw out 10+years of tooling and scripts, muscle memory and shorthand to fix a driver issue. I would read the wiki top to bottom and then go spelunking through other sources until I find the solution (then update the wiki) before I’d switch to something foreign with its own set of problems and unknowns.

    My advice is to find a distro that makes sense to you, and that has a deployment pattern you like and commit to it for a few years. Don’t switch unless you find something that fulfills those two requirements even better, and even then do so cautiously. Your experience and understanding is hard-won.









  • Daniel Quinn@lemmy.catoSelfhosted@lemmy.worldPost your bandwidth usage
    link
    fedilink
    English
    arrow-up
    43
    arrow-down
    1
    ·
    edit-2
    15 days ago

    What exactly are you self-hosting that’s gobbling up that much data? I’ve been self-hosting my website for decades and haven’t used that much over all that time let alone in one month.

    Most of my bandwidth consumption is from torrents and downloading Steam games, but even that doesn’t get me to even 1tb/month.


  • Hear me out: I want the prompt at the top of the screen.

    It’s terribly inconvenient to have the place you’re typping your command into at the bottom. On laptops, your fingers are in the way, and on desktops, you’re always craning your neck looking at the bottom-left.

    Imagine instead if your terminal looked like this:

    | ---------------------------------------------------------------------------- |
    | $ curl https://...
    | ---------------------------------------------------------------------------- |
    | $ echo "hello"
    | hello
    | $ ls
    | output.png
    | goes.txt
    | here.webm
    | ---------------------------------------------------------------------------- |
    

    After a command is entered in the upper pane, it’s appended to the lower pane along with the output just like a normal terminal. Maybe even something like translating Shift+Enter to mean “clear the output pane and run”.







  • Daniel Quinn@lemmy.catoComic Strips@lemmy.worldKrampus
    link
    fedilink
    English
    arrow-up
    42
    arrow-down
    5
    ·
    27 days ago

    So long as politicians are all painted with the same negative brush, there’s no room for anyone with a genuine interest in improving things. There are some truly great, caring people in politics working hard to do the right thing. It’s not their fault the public keeps voting for assholes.


  • You can’t really make them go idle, save by restarting them with a do-nothing command like tail -f /dev/null. What you probably want to do is scale a service down to 0. This leaves the declaration that you want to have an image deployed as a container, “but for right now, don’t stand any containers up”.

    If you’re running a Kubernetes cluster, then this is pretty straightforward: just edit the deployment config for the service in question to set scale: 0. If you’re using Docker Compose, I believe the value to set is called replicas and the default is 1.

    As for a limit to the number of running containers, I don’t think it exists unless you’re running an orchestrator like AWS EKS that sets an artificial limit of… 15 per node? I think? Generally you’re limited only by the resources availabale, which means it’s a good idea to make sure that you’re setting limits on the amount of RAM/CPU a container can use.