headquarter/openspec/changes/archive/2026-05-14-deployment-config/specs/traefik-label-generator/spec.md at 8b4784f5edfe99de6db5fec32729485f2b4b9ae0

alex/headquarter

Fork 0

Files

T

alex 8b4784f5ed

CI / Web CI (push) Failing after 10s

Details

CI / API CI (push) Failing after 11s

Details

chore(openspec): archive completed changes

- Archive config-secrets (FN-009) - 31 tasks complete
- Archive runfusion-poc (FN-008) - 25 tasks complete
- Archive deployment-config (FN-006) - 27 tasks complete
- All changes moved to openspec/changes/archive/

2026-05-16 11:33:37 +02:00

974 B

Raw Blame History

ADDED Requirements

Requirement: Tool spawn generates Traefik labels

The system SHALL generate Docker labels for Traefik when spawning a tool instance.

Scenario: Label generation on spawn

WHEN a tool instance is spawned
THEN the backend generates Traefik router and service labels
AND labels include rule, service, port, and TLS configuration
AND labels are stored with the tool instance metadata

Scenario: Label format

WHEN labels are generated for a tool instance
THEN router rule uses Host({subdomain}.{domain})
AND service points to the container's exposed port
AND TLS is enabled with certResolver

Requirement: Label generation handles multiple instances

The system SHALL generate unique labels for each tool instance.

Scenario: Unique router names

WHEN multiple instances of the same tool exist
THEN each instance gets a unique router name
AND no label collisions occur

974 B Raw Blame History