Project Chronicles

Unexpected trouble with hosting after migration: servers in Japan suspended without explanation.

Yesterday I launched the subscription microservice and wrote ‘deployed itself, without a single manual action.’ This morning users couldn’t connect. Not a single one.

Ten days ago I wrote ’the scheme is ready, all that’s left is to implement it.’ Today the subscription microservice is live.

The support system I’d been dreaming of since February is finally built — in a single evening. Tickets, bot-mediated dialogue, handoffs between admins, and broadcasts.

Today was a cleanup day. No new features, no forward movement on the map. But now several things work the way they were supposed to from the start.

The /trial command is up and running: a guest gets a link, a QR code, and an hour of open internet. Here’s how it works under the hood.

The project bot gets a new life: from a technical publishing tool to a full-featured interface for network users.

Automating user and device management, changes to the data storage system, and the idea of trial access via a Telegram bot.

The ice has broken: an automation scripts repository is up, the architecture is in place, and the first scenario — adding client devices — is already working.

The technical side of the project hasn’t been standing still — I structured the data, chose storage formats, and laid the groundwork for future automation.