docker-temporal

A set of project rules for running Temporal, a system that manages long-running background workflows, with Docker. It lists the required services, fixed image versions, ports, databases, and health checks.

In plain words
What is it for?
Starting Temporal infrastructure with Docker, configuring its PostgreSQL and Elasticsearch connections, creating namespaces, and checking whether the server is healthy.
Why use it?
It keeps the local Temporal setup consistent and helps prevent incompatible versions or services from being started incorrectly. Temporal's web dashboard is included for viewing the system.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/proyecto26/projectx/docker-temporal
Clone the repo
git clone --depth 1 https://github.com/proyecto26/projectx

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,975 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01975
Opus 5 $0.00000 $0.00988
Sonnet 5 $0.00000 $0.00395
Haiku 4.5 $0.00000 $0.00198

Measured yesterday against content hash d64f5b3b46c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docker-temporal scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/infraestructure/docker-temporal.mdc · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Docker Temporal Infrastructure

Temporal Services Overview

Services

  • temporal - Temporal server (Port 7233)
  • temporal-ui - Web dashboard (Port 8080)
  • temporal-admin-tools - One-time schema setup
  • temporal-create-namespace - One-time namespace creation

Image Versions (DO NOT CHANGE)

temporal:
  image: temporalio/server:1.29.2
temporal-admin-tools:
  image: temporalio/admin-tools:1.29.1-tctl-1.18.4-cli-1.5.0
temporal-ui:
  image: temporalio/ui:2.44.1

Temporal Server Configuration

Service Definition

temporal:
  image: temporalio/server:1.29.2
  depends_on:
    db:
      condition: service_healthy
    elasticsearch:
      condition: service_healthy
  environment:
    - DB=postgres12
    - DB_PORT=5432
    - POSTGRES_USER=${POSTGRES_USER}
    - POSTGRES_PWD=${POSTGRES_PASSWORD}
    - POSTGRES_SEEDS=db
    - ENABLE_ES=true
    - ES_SEEDS=elasticsearch
    - ES_VERSION=v7
    - DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development.yaml
  ports:
    - "7233:7233"
  volumes:
    - ./deployment/config/dynamicconfig:/etc/temporal/config/dynamicconfig

Health Check

healthcheck:
  test: ["CMD", "nc", "-z", "localhost", "7233"]
  interval: 5s
  timeout: 3s
  start_period: 30s
  retries: 60

Admin Tools (Schema Setup)

One-Time Setup Service

temporal-admin-tools:
  image: temporalio/admin-tools:1.29.1-tctl-1.18.4-cli-1.5.0
  depends_on:
    db:
      condition: service_healthy
    elasticsearch:
      condition: service_healthy
  environment:
    - DB=postgres12
    - DB_PORT=5432
    - POSTGRES_USER=${POSTGRES_USER}
    - POSTGRES_PWD=${POSTGRES_PASSWORD}
    - POSTGRES_SEEDS=db
    - ES_SCHEME=http
    - ES_HOST=elasticsearch
    - ES_PORT=9200
    - ES_VISIBILITY_INDEX=temporal_visibility_v1_dev
    - ES_VERSION=v7
  entrypoint: /deployment/scripts/temporal/setup-postgres-es.sh
  volumes:
    - ./deployment:/deployment
  restart: on-failure:6

What It Does

  1. Waits for PostgreSQL and Elasticsearch to be healthy
  2. Creates Temporal database schema in PostgreSQL
  3. Creates Elasticsearch visibility index
  4. Exits after successful setup
  5. Retries up to 6 times on failure

Read the full file on GitHub · 246 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 246 lines · 0 tokens per session scan A d64f5b3b46c5

Subscribe to this mod's changes

docker-temporal is a cursor rule published in the GitHub repository proyecto26/projectx (83 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,975 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.