Temporal Self-host POC

• What it is: A self-hosted Temporal server setup for orchestrating Healthcare platform-platform workflows (see salomatic_v2 #69, where Temporal is the central orchestrator). Contains docker-compose, instructions and reference snippets for client connections.
• Type / status / role: infra (devops/POC) · prototype · solo — all 6 commits by the user.
• Activity period: 2025-10-23 (one day, 6 commits). Setup spike.

• Temporal (temporalio/auto-setup + temporalio/admin-tools), self-hosted on port 7233.
• Docker Compose: Temporal server + admin-tools (tctl), connection to host PostgreSQL via host.docker.internal (extra_hosts: host-gateway), custom bridge network with a fixed subnet (172.25.0.0/16), healthcheck via tctl cluster health, SKIP_SCHEMA_UPDATE=false (auto schema migration).
• Snippets (reference implementations): worker/client/activities/workflows in Node.js/TypeScript (snippets/nodejs/src/*) AND Python (snippets/python/*) — a polyglot starter for the team.
• DB: host PostgreSQL (database temporal + dedicated user), separate setup SQL + pg_hba config.

6 commits in one day (solo):

• docker-compose for Temporal server + admin-tools against host Postgres.
• Postgres prep scripts (setup-postgres.sql, pg_hba_config.txt).
• README with instructions: start, status check, namespace management (tctl namespace register), logs.
• Reference worker/client snippets in TS and Python.
• Volume: compact infra foundation, not an application.

Confirmed by docker-compose/README:

• Self-hosting Temporal on host Postgres (instead of managed Temporal Cloud): connecting the container to the host DB via host.docker.internal + host-gateway, auto schema migration (auto-setup), healthcheck via tctl. → understanding of Docker networking and self-hosted orchestration.
• Polyglot reference snippets (TS + Python worker/client/activities/workflows): templates for connecting services on both stacks of the platform (Bun/Elysia + FastAPI). → a reusable starting point for the team.
• Fixed network topology (static subnet/IP) + namespace management via admin-tools.

• Sessions found: 0 (no directory). The repo has a .claude/.
• What was done with AI: no data.
• AI-workflow patterns: none.

• Working self-hosted Temporal stack (server + admin-tools + host Postgres) in docker-compose.
• Polyglot worker/client snippets (TS + Python).