parallel attribute support for serial_test
Experimental hermetic build engine with Starlark
Or, avoiding dealing with RabbitMQ clustering
In this week’s Yak shaving: Trying to write a Terraform Provider in Rust.
Continuing on my series about the infrastructure of a personal project. Last month I talked about the Terraform work and this month, it’s the Mitogen work.
TL;DR - there’s a list of Rust projects at the end of this post that want Hacktoberfest submissions, and are at least fairly decent ones :)
We’ve recently been travelling around a bit with our toddler (mostly to/from his nursery), and have occasionally run into the issue of a lift that isn’t working, which is a bit of an issue when you’ve got a buggy and a tired toddler that you’d really like to not have to navigate up some steps with. My partner prodded the internet wondering if there was any sites that provided such data, and some answers eventually came back.
Over the past couple of years I’ve been working on a particular side project. I’ve had the idea kicking around for a while, and planned on releasing it to the public (at least in a limited form) last year, but then 2020 happened, and we’re still in all of that in 2021, so there’s been a few delays. I’m still a way away from actually releasing anything, but now is a good time to talk about some of the infrastructure work there, as I think it’s worth sharing.
Before I start this I should clarify something: yes, I know it’s just a show for kids, and I’m a fan of the lessons and techniques it’s using behind the candy-coated facade. However it’s also weirding me out in various ways, and so I felt this needed discussing. I’ve only actually watched the first two episodes (along with my toddler), but I think this got enough of the core concept over that I can at least vaguely talk about this.
TL;DR: Proposal for a way to define multiple-machine systems in a immutable way, without requiring by-hand layouts.
Previous page Next page