Aerastrata
Notes, guides and patches

Developer

Everything that applies across the projects rather than to one of them: how they are built, how they are installed, what changed recently, and the house rules that keep seven repositories from drifting apart.

Status across all projects

Vixeov1.0.0
Live3 open
Coin Vaultv4.0.0
Live2 open
Mintv0.1.0
In progress2 open
EthaMailv0.1.0
In progress2 open
Viewrv0.1.0
In progress2 open
Musillowv1.0.0
In progress2 open
Docsv0.1.0
Experimental2 open

There is no single stack here, but there is a pattern. Anything with a phone client is Flutter, because one codebase covering Android and Linux desktop is worth more than platform-native polish on a project maintained by one person.

Anything that does real work behind a client is a server: Python where the work is data or modelling, Node where the work is protocol handling. The client stays thin enough that a second platform is a packaging job.

The exception is Docs, which is Kotlin, because it is a thin native wrapper around a server-side editor and Flutter would have added a layer without removing one.

FlutterDartKotlinPythonFastAPITypeScriptReactFastifyDocker

House defaults

Mobile clientFlutter
Native AndroidKotlin, when wrapping a server
Data backendPython, FastAPI
Protocol backendNode, Fastify
Web clientVite, React, TypeScript
Deploymentdocker-compose
LicenceMIT unless upstream says otherwise
TelemetryNone, in every project