Messaging

Signal, linked toa machine of your own

Signal Desktop, running on a Void Linux desktop of your own.Link it to your phone once, and the link survives a restart.

Signal 8.26.02 cores · 4 GBOpens in a browser tab

hub://signal

$ dxflow workflow create --identity signal hub://signal --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

Signal Desktop,without the desktop

The client is already installed. Link it to your phone and start.

Linked, not logged in

It joins your account as a linked device, so your phone stays the one in charge.

History lives on the disk

Signal keeps no cloud copy, so the volume holds the only history of the session.

Calls arrive silent

Calls and notifications arrive silent until you switch AUDIO on for the session.

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, which matters more here than most places.

PANEL and TASKBARBoth hidden, so the app has the whole screen. Show either one to get the desktop back.

AUDIOOff by default. Turn it on before you expect to hear a voice message or a call.

start it your way

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

$ dxflow workflow start signal --override env.app.AUDIO=on --link

The session

A desktop,just for this

Streamed to your browser, with Signal already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStoragethe link and the history

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.

Keep the session yoursSignal runs without its sandbox here, so do not pass the link on.

Good to know

Your messagesare on that volume

A linked device holds decrypted history. Think about the password and the link before you link it.

The session is the device

Anyone who reaches the tab reaches the conversation. A real VNC_PASSWORD is the whole of the protection here.

No sandbox

Signal starts with --no-sandbox because it runs as root inside the container. One more reason to keep the session to yourself.

amd64 only

There is no arm64 build published for this one, so it needs an x86-64 machine.

The image

Pulled once,then it stays

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

447Mamd64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

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

amd64 onlyOne architecture is published, so pick a machine that matches it.

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

Signal 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 Signal on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start Signal Browse workflows