Was macos at work, now Linux dev machine. Its a big up.
To be honest, all those are web apps now shrug. Zoom, slack, teams, docs, sheets, <insert word named app here>, all open in the browser. So IDC what the OS is for them. Linux Zero-Touch deployments are still in progress IMHO so I get why they arent here yet for a lot offices, but we are closer now than ever (thanks atomic OSs!).
Bazzite and Kinote. Vscodium and neovim. Vscodium is loaded up with nearly anything IaC or kubernetes related and Continue for some AI stuff (pointed to local and mistrial). Also heavy opinionated stuff for Python like black, etc (I want my ide to yell at me to make better code). Some GitHub and git lab add-ons too. Nvim is just as is.
Definitely overkill lol. But I like it. Haven’t found a more complete solutions that doesn’t feel like a comp sci dissertation yet.
The goal is pretty simple. Make as much as possible, helm values, k8s manifests, tofu, ansible, cloud init as possible and in that order of preference because as you go up the stack you get more state management for “free”. Stick that in git and test and deploy from that source as much as possible. Everything else is just about getting to there as fast as possible, and keeping the 3-2-1 rule alive and well for it all (3 backups, 2 different media, 1 off-site).
Fleet from Rancher to deploy everything to k8s. Baremetal management with Tinkerbell and Metal3 to management my OS deployments to baremetal in k8s. Harvester is the OS/K8S platform and all of its configs can be delivered in install or as cloudinit k8s objects. Ansible for the switches (as KubeOVN gets better in Harvester default separate hardware might be removed), I’m not brave enough for cross planning that yet. For backups I use velero, and shoot that into the cloud encrypted plus some nodes that I leave offline most of the time except to do backups and updating them. I user hauler manifests and a kube cronjob to grab images, helm charts, rpms, and ISO to local store. I use SOPS to store the secrets I need to boot strap in git. OpenTofu for application configs that are painful in helm. Ansible for everything else.
For total rebuilds I take all of that config and load it into a cloudinit script that I stick on a Rocky or sles iso that, assuming the network is up enough to configure, rebuilds from scratch, then I have a manual step to restore lost data.
That covers everything infra but physical layout in a git repo. Just got a pikvm v4 on order along with a pikvm switch, so hopefully I can get more of the junk on Metal3 for proper power control too and less IPXE shenanigans.
Next steps for me are CI/CD pipelines for deploying a mock version of the lab into Harvester as VMs, running integrations tests, and if it passes merge the staged branch into prod. I do that manually a little already but would really like to automate it. One I do that I start running Renovate to grab the latest stable for stuff for me.
As THE USB-C PD evangelist. I have to say. Fair. Like PD EPD is definitely reaching the limits of the USB-C form factor to me, and data over copper is a dead end at some point too.
Still want ever device I have on it. Though as we scale past the 260 watt range (and I do…) or longer distances (also me) it’s just going to have to be another interface and probably medium for data for the protocol. So far MPO for data and honestly pogo pins for power are the best I’m seeing.
Again for everything thats not a serious power device like well pumps, servers, AC/Heat pump, Power tools, etc or serious data server/client. Its fine, which is seriously impressive.
Rant over I also like the idea of better hardware stats reported to the OS. Its one reason I fell in love with software raid over hardware raid
Git lab CI is my goto for git repo based things (unit tests, integration tests, etc). Fleet through Rancher for real deployments (manages and maintains state because kubernetes). Tekton is my in between catchall.
Are people paying for SteamOS? I thought the only revenue streams around it was the Steam Deck and soon the Steam Machine and the VR thing.
Largely it’s a risk reduction thing for them. Otherwise their dependent on a monopolistic OS and their largely uninterested in collaboration competitor.
Servo is the one I follow in that space
Hopefully work on opensource firmware getting going like https://github.com/koalazak/dorita980. Seems more movement in the server side though https://github.com/ia74/roomba_rest980
Another option is hardware hacking it https://github.com/meech-ward/roomba/tree/main
Tbh the amount of cameras and microphones we have that upload to external unaudited servers (“the cloud”) is insane to me. This is just further worry about it since the scheme allowed their ownership over our devices and privacy, which means they can also sell that.
This is how I use kubernetes (specifically Harvester HCI and some lighter RKE2 nodes). Just one big computer lots of nodes. Still working getting the plumbing fully figured out for virtual desktop to output video devices.
Even better tbh
Sick and native Wayland support
Buying Doom the Dark Ages now. Hell yeah for them!
Honestly. I think private companies can have a place in public infra, but it’s not in the freaking ownership. Rent seeking is the worst and most destructive aspect of private ownership and we’ve known and can look at countless example of that since Adam Smith!
No no those kids giving up education in order to keep their family afloat aren’t being coerced or forced at all /s
The US admin also repeal anti slavery laws for migrant workers couldn’t have more blatant on how they actually feel about the working class. The anti immigrant retoric here about “jobs” has always been a lie
Removed by mod
Check out ptyxis as well. Terminal with support for opening new tabs into the container namespaces.
Honestly tinkering like this is a lot more stable for me. If I bork it, I can just blow it away. I just need to get better about going from tinker to full Containerfile for my build environments lol
Not the IP but hope this git link helps: https://gitlab.com/here_forawhile/nanogram.git
Tar ball link if that is better for you: https://gitlab.com/here_forawhile/nanogram/-/archive/main/nanogram-main.tar.gz?ref_type=heads