Graphics

The whole editor,in a browser tab

The full desktop GIMP, on a Void Linux desktop of your own.Open a file from the volume, and save it straight back.

GIMP 3.2.42 cores · 4 GBOpens in a browser tab

hub://gimp

$ dxflow workflow create --identity gimp hub://gimp --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

Photo work,without the install

Open the file, work on it, and save it back to the volume.

Layers and masks

Composite in layers, mask what you keep, and change your mind at any point.

Retouch and paint

Clone, heal and paint with the whole brush engine, on an image of any size.

Script-Fu batches

Run it headless across a folder on the volume, with Script-Fu or Python-Fu.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.

PANEL and TASKBARBoth hidden, so the editor has the whole screen. Show either one when you want the docks on separate windows.

AUDIOOff here. Turn it on and the desktop sound is streamed beside the picture.

start it your way

$ dxflow workflow start gimp --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start gimp --override env.app.TASKBAR=show --link

The session

The editorfills the screen

Streamed to your browser, with GIMP already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStorageyour files, kept between runs

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

Big images wantmemory, not pixels

The screen is streamed, so what limits you is what the machine can hold, not what your laptop can draw.

Size it for the file

A large composite with many layers is a memory problem. Pick the machine for RAM and the editing stays responsive.

Built on Void

The smallest desktop base the hub has, which is why a full image editor pulls in well under half a gigabyte.

Work belongs on the volume

Keep the XCF and the exports under /volume. Anything saved elsewhere goes when the machine does.

The image

Pulled once,then it stays

GIMP arrives as one image. This is what comes down the first time, and what the disk should have free for it.

433Mamd64compressed, the way the registry counts it

425Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/gimp:latestPublished from the hub, pulled on the first start and kept for the ones after it.

Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.

What it asks for

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.

2 cores · 4 GBAsks forwhat the definition writes down

2 cores · 2 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

GIMP asks for 2 cores and 4 GB. Cheapest first.

E2 Medium

$0.0419/ hour2 cores · 4 GBStart this machine

T3 Medium

$0.052/ hour2 cores · 4 GBStart this machine

B2s

$0.052/ hour2 cores · 4 GBStart this machine

Run GIMP on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start GIMP Browse workflows