Vector work,on a machine of your own
The full desktop Inkscape, on a Void Linux desktop of your own.Draw here, and the SVG lands on the volume as a file.
$ dxflow workflow create --identity inkscape hub://inkscape --start --link
Plain SVG,and nothing but
Illustrations, icons, logos and diagrams, in an open format.
Draw with beziers, edit every node, and take the union or difference of two.
It reads and writes plain SVG, the same file your browser reads, no lock-in.
Convert or export whole folders from the command line, with no GUI in sight.
Every defaultis one override away
The session reads its settings from the environment, so you set them on the start line.
$ dxflow workflow start inkscape --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start inkscape --override env.app.TASKBAR=show --link
The canvasgets the whole screen
Streamed to your browser, with Inkscape already maximized.
The drawingis a text file
An SVG is markup, which is why Inkscape fits so easily into work that is otherwise automated.
A figure your script wrote opens the same as one you drew. Fix the labels by hand and write it back out.
Open a terminal in the desktop and convert, export or query a document without touching the canvas.
Keep the SVG and whatever you export from it under /volume, and the next start opens where you stopped.
Pulled once,then it stays
Inkscape 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
Inkscape asks for 2 cores and 4 GB. Cheapest first.