A painting studio,in a browser tab
Krita, on a Void Linux desktop of your own.Brushes, layers and animation, on a machine bigger than your laptop.
$ dxflow workflow create --identity krita hub://krita --start --link
Built for painting,not for photos
Krita is an illustration tool first, and the brush engine shows it.
Dozens of engines, stabilizers and wrap-around mode, all of them editable.
Filter, clone and transform masks that stay live while you keep painting.
An onion-skinned timeline, exported to a sequence or a video on 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 krita --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start krita --override env.app.TASKBAR=show --link
The canvasfills the screen
Streamed to your browser, with Krita already maximized.
A mouse is nota pressure-sensitive pen
The session is streamed as pixels and input, and a tablet on your desk does not reach through it.
What arrives is cursor position and clicks. Brushes that key off pressure behave as though you pressed the same amount every time.
A large multi-layer painting is a memory problem before it is anything else. Pick the machine for RAM.
Keep the KRA and the exports under /volume, and the next start opens with your document still there.
Pulled once,then it stays
Krita 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 4 cores and 8 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
Krita asks for 4 cores and 8 GB. Cheapest first.