Alex Kretzschmar

I just like the fact that the nodes are completely disposable.

You know, the storage... For years, you've written Ansible playbooks to configure nodes and install packages and do this and do that.

And now I have a declarative file that says, system, do this.

And when it bootstraps itself...

It doesn't know what it is until you give it that instruction, and then it just figures it out.

There's no config drift.

It's impossible for there to be config drift.

It just is what I tell it to be exactly, and the only way to make a change is to update the config so it gets versioned, it gets...

All the niceties of that.

That's kind of what Bootsy is, right?

Yep, yep, yep.

It's the same idea.

Different implementation, but same idea.

For a home server.

I don't want to have to do an apt-get to upgrade every six weeks and then have something break and suddenly my server doesn't boot anymore.

It would be nice if I could just update a config file, push that to Git, and then it just figures it out and reconciles those changes, a bit like Argo CD and Flux do in the Kubernetes world.

but at the OS level.

That's what I want.

That's the world I want to get to.

Push a configuration change to Git, and then my server just figures it out.