headquarter/openspec/changes/deployment-config/specs/subdomain-routing/spec.md at 78aaddb2b5f85b445b889ad23b3021ed9991efc3

alex/headquarter

Fork 0

Files

T

alex 78aaddb2b5

CI / Web CI (push) Failing after 12s

Details

CI / API CI (push) Failing after 1m1s

Details

docs(openspec): add OpenSpec changes for FN-005, FN-006, FN-008, FN-009, FN-010

- Add frontend-foundation change (FN-005) with 46 tasks
- Add deployment-config change (FN-006) with 27 tasks
- Add runfusion-poc/opencode-poc change (FN-008) with 25 tasks
- Add config-secrets change (FN-009) with 31 tasks
- Add codeserver-spawn change (FN-010) with 38 tasks
- Include project specsheet and configuration
- Archive completed deployment-config change

2026-05-14 17:35:20 +02:00

919 B

Raw Blame History

ADDED Requirements

Requirement: Each tool instance gets a unique subdomain

The system SHALL assign a unique HTTPS subdomain to each running tool instance.

Scenario: Subdomain pattern

WHEN a tool instance is spawned
THEN its subdomain follows {tool}-{project}-{user}.{domain}
AND the subdomain is deterministic based on instance metadata

Scenario: Subdomain accessibility

WHEN a tool instance reaches running status
THEN its subdomain resolves via DNS
AND Traefik routes the subdomain to the container
AND the user can access the tool via the subdomain URL

Requirement: Subdomain is released on stop

The system SHALL remove Traefik routing when a tool instance stops.

Scenario: Stop removes routing

WHEN a tool instance is stopped
THEN Traefik labels are removed or disabled
AND the subdomain no longer routes to the container

919 B Raw Blame History