Temporal

Runs Temporal 1 · macOS & Linux · registry page ↗

A local Temporal dev server: a single pure-Go binary bundling the Temporal services, a SQLite store, and the Web UI, with no JVM or Docker. Supervised and always-on (workers long-poll it); connect via TEMPORAL_ADDRESS.

Usage

module temporal "dev" {
  version = "1.1"
  port    = 7233
  ui_port = 8233

  namespace "orders"  {}
  namespace "billing" {}
}

Versions you can declare

The version = you write is the engine’s own version — the only version that’s yours. Declare a series and doze pins its newest published build, or declare an exact build; either way it’s fetched, verified, and pinned in doze.lock (so it never moves on its own).

version =	pins (today)	exact builds
1.0	1.0.0	1
1.1	1.1.2	3
1.2	1.2.0	1
1.3	1.3.0	1
1.4	1.4.1	2
1.5	1.5.1	2
1.6	1.6.2	3
1.7	1.7.3	4
1.8	1.8.2	3

Every exact build, per series

1.0 — 1.0.0

1.1 — 1.1.2 · 1.1.1 · 1.1.0

1.2 — 1.2.0

1.3 — 1.3.0

1.4 — 1.4.1 · 1.4.0

1.5 — 1.5.1 · 1.5.0

1.6 — 1.6.2 · 1.6.1 · 1.6.0

1.7 — 1.7.3 · 1.7.2 · 1.7.1 · 1.7.0

1.8 — 1.8.2 · 1.8.1 · 1.8.0

Configuration

Field	Type	Default	Description
version	string	—	temporal CLI version Required.
port	number	7233	frontend gRPC port
ui_port	number	8233	Web UI port
headless	bool	false	disable the Web UI
namespace	block	—	a namespace to create (repeatable; label = name; retention, description)
restart	block	—	supervisor restart policy (policy, backoff, max_retries)

Module releases

Machinery, for the curious: the plugin releases that provide this engine. doze selects the newest compatible one and pins it in doze.lock — you never write these. Older releases stay resolvable for pinned lockfiles.

Release	Engine versions	Platforms
0.2.2	1	3	stable
0.2.1	1	3

Raw signed data: index.yaml ↗ · meta.yaml ↗