Utilities

Transfers,into the volume

FileZilla, on a Void Linux desktop of your own.FTP, FTPS and SFTP, pulling straight onto the disk the runs read.

FileZilla 3.69.32 cores · 4 GBOpens in a browser tab

hub://filezilla

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

Pull it here,not to your laptop

The transfer happens on the machine, at the machine's bandwidth.

Three protocols

FTP, FTPS and SFTP, with a site manager that remembers the credentials.

A queue that resumes

Large transfers survive an interruption and pick up where they stopped.

Straight to /volume

What lands there is what the next workflow on the machine reads.

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 transfer window has the whole screen. Show either one to get the desktop back.

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

start it your way

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

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

The session

The transfer windowfills the screen

Streamed to your browser, with FileZilla 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

The transfer happenson the machine

Files move between the remote server and the volume directly. Your laptop is not in the path.

Pull it down to /volume

A dataset arrives on a cloud link rather than a home one, and lands where the next workflow already reads.

The site manager keeps passwords

Saved credentials sit in the profile on the volume. Protect the session as you would protect them.

For a bucket, use S3 Sync

FTP, FTPS and SFTP are what this speaks. Object storage belongs to the step built for it.

The image

Pulled once,then it stays

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

406Mamd64compressed, the way the registry counts it

401Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/filezilla: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

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

E2 Medium

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

Start FileZilla Browse workflows