Skip to main content
Super Durable
English
English简体中文
GitHubLog inSign up Cloud
Menu

Web (Dex Web)

View as Markdown

Dex Web is the operator UI for Dex. Use it to find Flows, follow a run, read its inputs, Attributes, and failures, and act on it.

What it shows​

  • Search and Summary find Flows and show their state.
  • The run page shows a run's active Steps, Attributes, and Channels. Its Timeline lists each event of the run. The event panel shows the event's inputs, outputs, and Attribute changes.
  • The Flow canvas draws a Flow's Steps and transitions from its Flow Definition Graph. The dexcli visualize analyzer produces this graph from Flow source.
  • Start Flow starts a Flow, and Actions call RPCs on a selected run.
  • Experimental features, such as Designs, Work Queue, Connectors, and the Agent session view, show only when they apply.

How it fits with the other components​

Dex Web runs as its own process. It connects to the server API, the same API that Workers and Clients use. A Flow that Dex Web starts runs on your Workers. Dex Web also configures Connectors for local development.

Dex Web reads Flow Definition Graphs from the server. Workers or dexcli publish them there. Dex Web can also read graphs from a directory. The directory is optional. When both have a graph for one Flow type, the directory wins.

Dex Web validates each graph on its own. An invalid graph shows its error. The other Flow types keep working.

Run it​

  • dexcli dev starts Dex Web together with a local server-zd.
  • dex-web is a standalone binary and container image for production.
  • dexcli web serves Dex Web against an existing server, for example over an SSH tunnel.
dex-web --flow-service-address 127.0.0.1:8801

Dex Web has no end-user authentication. Place it behind TLS and an authenticating reverse proxy, and never expose it to the public Internet.

Reference​

The Web reference covers the dex-web settings, access control, each UI page, the Flow source analyzer, and a read-only debugging workflow.