'%20d='M364.9%20143.2v98.9l-1.4%201.2-165.6%20140.4%2035.7%2029.7v-34.2l1.4-1.2%20123.4-105.4%206.5-5.6v37l-1.3%201.2-99.7%2085.8v84.7l-6.6-5.7-97-83.1-3.6-3%203.5-3%20174.4-150.6v-25.1L153.7%20360.5l-6.6%205.7v-98.9l1.4-1.2%20161.6-138-35.7-29.7v34.4L273%20134%20153.7%20236.7l-6.6%205.7v-37l1.3-1.2%2097-83.2V36.3L252%2042l97.1%2083.1%203.6%203-3.6%203-171.7%20147.7V304l106.2-90.6%2056.4-48.8%2018.3-15.7z'%20/%3e%3c/svg%3e)
Development
The desktop editor,on a desktop you rent
Visual Studio Code on an Ubuntu desktop of your own.The application itself, not a browser build of it.
VS Code 1.912 cores · 4 GBOpens in a browser tab
hub://vscode
$ dxflow workflow create --identity vscode hub://vscode
$ dxflow workflow start vscode --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
The real editor,not a web build
The desktop application, with Miniconda and Copilot alongside.
The desktop build
The application itself, not a browser port of it, on a real desktop.
Miniconda included
conda sits on the PATH, so Python environments work from a terminal.
Extensions persist
The profile and the extensions directory both sit on the volume too.
The session
The editorfills the screen
Streamed to your browser, with VS Code already maximized.
6082Browserin the tab, at /vnc.html
5901VNCin a native client
/volumeStoragesettings, extensions, code
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 yoursIt runs without its sandbox here, so do not pass the link around.
Run VS Code Server on your own machinePick a machine that meets it, and it opens about a minute after you ask.