Canadian software engineer living in Europe.
As this is your first go, I’d recommend not tinkering with USE flags at all. Take the defaults, find what you don’t like, and consider tweaks later. USE flags can end up like a sort of “dependency hell”, with one package not working correctly because it expects another package to have something you’ve excluded. It’s uncommon, but frustrating when it happens. It’s best to start with the defaults.
I like this alot.
How would you reset the timer whenever input is detected though?
I’ve had a really hard time figuring out how to get cloud native pg working 'cause I couldn’t get longhorn working for disk space.
So instead I went with a separate Raspberry Pi that isn’t part of the cluster to host a single Postgres instance.
It’s inelegant, but has worked for years. Still, I’d rather host a separate pg instance for each project… I just have to figure the above out first.
Ferengi rule of aquision #285: “No good deed ever goes unpunished”.
#Solarpunk!
This feels oddly specific, like there’s a famous map out there with Carter and a rabbit. Anyone know what he’s talking about?
Edit: I found the Wikipedia article about the incident, but no map yet.
I have Arch on my desktop, and all my laptops, but all of my servers run Debian. If you want your machine to have all the latest stuff, then Arch is great. If you want it to Just Work™ all the time without any concerns, Debian is great.
This would be much less of a problem if fewer people insisted on bringing their whole living room everywhere they go.
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.2.3) and push it to the repo. This would trigger a build and push the resulting image into the container registry.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.3k8s/chart/environments/staging.yaml: tag: 1.2.2k8s/chart/environments/production.yaml: tag: 1.2.2Once 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_HOST}" 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”.
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’ve had Gentoo (and later, Arch) on my Surface Pro 3 for a decade. It’s fully supported, touch screen and all.
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.
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.
Why hasn’t he migrated to something more stable?
Don’t be that guy.
I know it’s supposed to be a joke how a nerd will spend six hours writing a script to automate a 30second task but… it’s not really funny.
Working with less-experienced developers, I’m amazed at how slow everything is for them: No keyboard shortcuts, no automated scripts, just slow, plodding mouse-driven tinkering.
Automation, shortcuts, and scripting drive your ability to iterate and therefore learn.
Train your fingers, and spend those hours automating repetitive stuff. It’s worth it.
The aversion to using a GPL library is a red flag for me. It basically says: “we don’t want to grant our users the same rights we have”.
I started using it 'cause I was working with a lot of Linux nerds and they convinced me to try it out. I liked the politics of the GPL and the potential in the Free ecosystem.
25 years later I refuse to use anything else. Windows & Mac are built to take options away from you, to force you do use your hardware their way, and I hate it. My machine does exactly what I want it to, with hundreds of keyboard shortcuts and a solid UI built atop transparent subsystems. Windows ties my hands while pushing ads and AI into my eyeballs. Mac only “Just Works” if you’re using it precisely the way that want you to and exclusively with other iShit. No thanks.