My girlfriend’s dad had hundreds of movies on VHS, pirated from cassettes he’d rented in the past and copied at home by chaining two VCRs together over coaxial cable.

Software was wild pre-internet. My buddy had Windows 95 on 42 3¼" floppies that we copied onto additional sets of 42 floppies that we kept in heavy boxes and then painstakingly installed onto computers belonging to friends and family around the neighbourhood.

I also had a whole bunch of audio cassettes that contained music I dubbed from radio, other cassettes, and later CDs (burning your own was at first, impossible, and later, expensive).

I’m 46.

This would be much less of a problem if fewer people insisted on bringing their whole living room everywhere they go.

Crushing labour is a key part of any growth plan. When they say “growth”, they mean short term profits (line go up), not improvements in quality of life.

Seriously, fuck that guy and all his fossil friends.

FFS. We really deserve to live in a world on fire.

I’ve used FluxCD in the past and have looked into ArgoCD, but honestly, I’ve not seen any big benefit from either to be honest. I use k8s both at home and at work, and in both cases, we do “imperative” deploys: you run helm install ... either directly or via the CI and stuff is deployed.

So for example at my last job, our GitLab CI just had a section triggered exclusively for merges into master that ran helm install ... for all three environments. We had three values.yaml files, one for each environment, and when we wanted to deploy a new version, the process was:

1. Create a tag for our release version (ie. 1.2.3) and push it to the repo. This would trigger a build and push the resulting image into the container registry.
2. Push an update to the repo with the new tag set in the appropriate Helm values file. If we wanted to deploy 1.2.3 to development but not yet to staging or production, then the tag: value in each of the environment files would look like this:

• k8s/chart/environments/development.yaml: tag: 1.2.3
• k8s/chart/environments/staging.yaml: tag: 1.2.2
• k8s/chart/environments/production.yaml: tag: 1.2.2

Once that change is pushed, the CI will automatically apply it with helm install ... and make sure that all three environments are what they’re supposed to be.

As for dependent services, that should all be in your Helm chart so they’re stood up and torn down together. The specific case you mention about “Service A” being dependent on “Service B” but stood up before “Service B” is ready is a classic problem, but easily solved:

The dependent service (“A” in this case) should have an entrypoint that checks for everything else before starting. Here’s what I’m using right now in a project:

#!/bin/sh

while ! nc -z postgres 5432; do
  echo "Waiting for postgres..."
  sleep 0.1
done
echo "PostgreSQL started"

touch /tmp/ready

exec "$@"

I’ve even got some code that checks that all the Django migrations have run first for the same situation. The Kubernetes philosophy is that any container should be able to die at any time and be eventually be brought back up and that every container needs to be prepared for this. Typically this means that your containers should operate on the basis of “if I can’t work, die, and hope the problem is solved by the time Kubernetes redeploys me”.

If you’re in Vancouver, go to Lee’s instead. Actually Canadian, and arguably the best doughnuts on the planet (I’ve checked!)

Kubernetes. For a homelab, the stripped-down k3s is fantastic and surprisingly easy to get going.

Once you’ve got Kubernetes set up, you can lean on all the many tools already out there for things like deploying complex projects (Helm) and monitoring (Prometheus/Grafana). OpenLens is a nice piece of software you can use to monitor and control your cluster too, as is k9s.

I’ll just leave this here.

I’ve had Gentoo (and later, Arch) on my Surface Pro 3 for a decade. It’s fully supported, touch screen and all.

I was really happy to hear Lewis say on multiple occasions that the NDP strategy should be low-level, community organising. Getting people to come out and make signs, knock on doors, and talk about policy is how the Left is built. Slactivism has hollowed us out, and it’s great to see some push back here.

1. The banning of all future fossil fuel expansion.
2. Criminal charges for any Canadian fighting in the IDF or involved in sending arms to Israel.
3. Require that all vehicles in excess of 2 tonnes require a commercial license to operate. The idea would be that this limit would gradually be reduced to a sensible number over time.
4. Vehicle speed limiters, ideally tied to the region you’re in (city/highway).

I know, you asked for one, but there’s a lot of stuff to be done.

As this is a new project, have you considered hosting your code somewhere other than GitHub? Codeberg and GitLab are similarly user-friendly platforms without the many downsides of supporting Microsoft.

Fucking Americans man…

A platform that’s down 10% of the time and that now has a reputation of locking people out of their accounts without reason for weeks at a time cannot, under any definition of the word, be considered “stable”.

I just… don’t get it. This whole community, we’re supposed to be building stuff for ourselves and each other, and for some reason people keep going to bat for a company that demonstrably holds every one of us in contempt.

Just… stop using their shitty tools already.

I’ll just leave this here.

Why hasn’t he migrated to something more stable?

Don’t be that guy.

This “1000 words to conversational” sourdough sounds really good to me. Thanks for sharing!

Oh I didn’t know this was available in Codeberg! Thanks for sharing.