Developer
070cd4d5a5
Add generated .pi-map.md and .pi-map.index.md files across the repository so the project navigation maps are shared and versioned. These artifacts are maintained by project_map_init/patch/validate and must be kept in sync with source edits. Note: .cache/ remains ignored (added in previous commit).
23 lines
1.5 KiB
Markdown
23 lines
1.5 KiB
Markdown
# openspec/changes/archive/2026-05-22-instance-proxy
|
|
dir: openspec/changes/archive/2026-05-22-instance-proxy
|
|
|
|
index: openspec/changes/archive/2026-05-22-instance-proxy/.pi-map.index.md
|
|
|
|
## role
|
|
Defines an archived OpenAPI specification and design documents for a FastAPI-based HTTP/WebSocket proxy to expose internal Docker tool instances through authenticated external endpoints.
|
|
## files
|
|
- .openspec.yaml | Defines an OpenAPI specification configuration file with schema type and creation date metadata
|
|
- design.md | Design document for implementing a FastAPI-based HTTP/WebSocket proxy to allow users to access internal Docker tool instances through a single authenticated API endpoint. | dep: FastAPI, httpx, starlette.websockets, Docker
|
|
- proposal.md | Proposes adding an HTTP/WebSocket proxy endpoint to expose Docker containerized tool instances to users over HTTPS instead of broken localhost links | dep: docker, backend API, frontend, WebSocket, HTTPS
|
|
- tasks.md | Project task tracking checklist for implementing a proxy endpoint system that routes HTTP/WebSocket traffic to Docker container instances | dep: Docker, FastAPI/httpx, WebSocket, code-server, ruff, mypy
|
|
## arch
|
|
Specification-driven API design using OpenAPI/OpenSpec configuration, FastAPI async proxy architecture with HTTP/WebSocket dual-protocol routing, Docker container instance targeting, and task-tracked iterative implementation.
|
|
## tags
|
|
docker, websocket, design, fastapi, http, proxy, instances, endpoint
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|