Temporal UI

Nota bene: This is pre-release software.

Prerequisites

Temporal must be running in development. (For details, see Run a dev Cluster in the documentation.)

Trying it out

After pulling down the lastest version of Temporal's docker-compose, you can access the new new UI by visiting http://localhost:8080.

Trying it out: Bleeding edge

Starting the UI API server will give you a somewhat recent version on localhost:8080. If you want to use the most recent commit to main, you can spin up a bleeding-edge build as described below.

Once you have the prerequisites going, run the following:

npm run build:local
npm run preview:local

Developing

Developing the UI has the same prequisites as trying it out. Once you've created a project and installed dependencies with npm install, start the development server:

npm start

By default, the application will start up with a version of the UI for the local version of Temporal. You can start the UI for Temporal Cloud by setting the VITE_TEMPORAL_UI_BUILD_TARGET target to cloud. Alternatively, you can use either of the following scripts:

npm run dev:local
npm run dev:cloud

Building

The Temporal UI must be built for either the local version or Temporal Cloud. You must set the VITE_TEMPORAL_UI_BUILD_TARGET environment variable in order to build the assets. This will be set for you if you use either of the following npm scripts.

npm run build:local
npm run build:cloud

The resulting assets will be placed in either build-local or build-cloud respectively.

You can preview the built app with npm run preview, regardless of whether you installed an adapter. This should not be used to serve your app in production.

Configuration

Set these environment variables if you want to change their defaults

Variable	Description	Default	Stage
VITE_API	Temporal HTTP API address. Set to empty `` to use relative paths	http://localhost:8080	Build
VITE_MODE	Build target	development	Build

Developing with Holocene

To see updates from holocene, follow the instructions in holocene README and link the project after cloning:

npm link holocene

Developing with Canary

To get a better representation of production data, you can run our UI with the canary-go repo. You will need go installed on your machine.

canary-go

make bins
./temporal-canary start

temporal

make bins
TEMPORAL_ENVIRONMENT=development_sqlite make start

tctl

make build
./tctl --ns canary namespace register
./tctl --ns default namespace register (if you also want a default namespace)
./tctl --auto_confirm admin cluster add-search-attributes \
	 --name CustomKeywordField --type Keyword \
	--name CustomStringField --type Text \
	--name CustomTextField --type Text \
	--name CustomIntField --type Int \
	 --name CustomDatetimeField --type Datetime \
	--name CustomDoubleField --type Double \
	--name CustomBoolField --type Bool

To view the search attributes code: https://github.com/temporalio/docker-builds/blob/main/docker/auto-setup.sh#L297

ui-server

make build-server
./ui-server start

ui

npm start