Canadian software engineer living in Europe.

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

help-circle
  • It’s funny, I flocked to Steam because I was under the impression that I was owning the games. While other companies were trying to get me to sign onto their “play everything” subscriptions and Google had their “Stadia” (remember them?), Steam let me download the game and install it on my (Linux!) computer with no license key checks, working offline etc. etc. I feel like the assumption that I was in fact buying my games, rather than a license to play them when Steam saw fit was a reasonable one. This discovery was quite enraging.







  • Daniel Quinn@lemmy.catoSelfhosted@lemmy.worldLiquid Trees
    link
    fedilink
    English
    arrow-up
    91
    ·
    18 days ago

    I had the same reaction until I read this.

    TL;DR: it’s 10-50x more efficient at cleaning the air and actually generates both electricity and fertiliser.

    Yes, it would be better to just get rid of all the cars generating the pollution in the first place and putting in some more trees, but there are clear advantages to this.













  • Daniel Quinn@lemmy.catoSelfhosted@lemmy.worldPost your bandwidth usage
    link
    fedilink
    English
    arrow-up
    42
    arrow-down
    1
    ·
    edit-2
    5 months 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.



  • 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.