Project Diary

While I was chopping down maples and opening the dacha season, the project kept moving. Yesterday I finished building the Architecture 2.0 infrastructure and ran a full end-to-end test. First traffic is flowing.

Two empty clusters waited in the cold for their first tenants: data moved into etcd, and k3s welcomed its first service — a database API built on FastAPI.

First component: the management cluster on Kubernetes.

The concept behind Architecture 2.0.

Architecture 2.0 is taking shape — time to build. First component: a Kubernetes management cluster. But before any logic or services, there’s one question that comes first: security.

Bot fixed, Habr conquered, personal site under construction, Rustlings resurrected. How do I manage it all? I don’t.

Infrastructure up, bot running — and then it turns out it can’t do anything. The cost of overly tidy containerization.

The Root node has been running for five days. Today I brought up the supporting infrastructure: the admin bot and the subscription microservice — both containerized, with auto-deploy.

Had to unholster the server I’d been keeping in reserve. But the network is up.

A short busy week with no time for the project, support still silent, the network on pause — and some thoughts about eggs, baskets, and diversification.