Draw the glyphs,then ship the font
FontForge, on a Void Linux desktop of your own.Outlines, metrics and hinting, out to TTF, OTF or WOFF on the volume.
$ dxflow workflow create --identity fontforge hub://fontforge --start --link
An outline editor,and a compiler
Draw the letter, set what it does beside its neighbours, then generate.
Bézier editing per glyph, with references so an accent is drawn once.
Widths, side bearings and kern pairs, checked in a live metrics window.
TrueType, OpenType, PostScript, SVG and WOFF, written out to the volume.
Every defaultis one override away
The session reads its settings from the environment, so you set them on the start line.
$ dxflow workflow start fontforge --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start fontforge --override env.app.PANEL=show --link
The font viewfills the screen
Streamed to your browser, with FontForge already maximized.
It opens on a fontthat does not exist yet
There is no file chooser waiting. You get an empty font called Untitled1, so there is somewhere to work immediately.
The blank font is there to be used. An existing one comes in from File and Open, off the volume.
Editing a character opens its own window. Show the panel when you have more of them open than you can find.
Keep the SFD and whatever you generate from it under /volume, and the next start finds both.
Pulled once,then it stays
FontForge arrives as one image. This is what comes down the first time, and what the disk should have free for it.
What it wants,and what it needs
The definition asks for 2 cores and 4 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.
Machines that fit it
FontForge asks for 2 cores and 4 GB. Cheapest first.