Sigil Gate Project Blog

The blog went quiet — not because of failure, but the opposite. On overdosing on success, a forced stop, and coming back.

Setting up a server, I delegated the configuration to an AI agent — and one unexpected step pulled me into the world of cryptography for half an hour. Here’s how the locks of the digital world actually work.

Revived an old pet project of a learning platform and built a minimalist coding trainer — with a container pool for each language and vim as the IDE.

One more reason for the silence: while reorganizing my workspace, I built a small project — a browser terminal for an AI assistant, accessible from any device.

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.

The control cluster is deployed, data migrated, API serving over HTTPS. A long list of things still ahead — here’s how to pick only what’s strictly required to get the network running.

On conservatism, habits, and technologies that change faster than you can get used to them.

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.

The etcd cluster is up and waiting for data. Here’s why copying everything over as-is didn’t work out — and how the migration turned into a full rethink of the data schemas.

First component: the management cluster on Kubernetes.