The desktop the restof the hub builds on
A full Ubuntu desktop, drawn in the tab through noVNC.The same image every GUI workflow in the hub starts from.
$ dxflow workflow create --identity ubuntu hub://ubuntu --start --link
Familiar ground,rented by the hour
LTS packages and apt, on a desktop that is already running.
Every other GUI workflow builds on this image, so apt behaves the same way.
Openbox, a taskbar, a terminal and a file manager, over TurboVNC and noVNC.
Anything you keep under /volume is still there once the next start is done.
Six variablesshape the desktop
What you see and what you hear are both set on the start line, and nothing has to be edited inside.
$ dxflow workflow start ubuntu --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start ubuntu --override env.app.AUDIO=on --override env.app.AUDIO_RATE=44100 --link
The whole desktop,not just one app
Streamed to your browser, with the panel and taskbar shown.
This is the basethe others stand on
Most of the GUI entries in the hub are this desktop with one application on top of it.
Take this image, add the package you need, and you have the same session with your tool in it. That is how the rest were made.
Browsers keep a page muted until someone interacts with it, so audio starts at the first click or keystroke in the desktop.
The audio client follows AUDIO_PORT, so give each session its own port and match the audio mapping beside it.
Pulled once,then it stays
Ubuntu Desktop 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
Ubuntu Desktop asks for 2 cores and 4 GB. Cheapest first.