Decompose: Service documentation (architecture, deployment, performance, development) — Phase 2: Deployment + operations #61
Labels
No labels
blocked:children
blocked:depends-101
blocked:depends-103
blocked:depends-104
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:preflight
bug
chore
feature-request
in-progress
lint-cleanup
needs-decompose
performance
quality
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/easystitch#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Phase 2: Deployment + operations
Goal: "How do I run this in production." Covers Docker, node_hub,
env vars, log format, healthcheck, monitoring, common failure modes.
Files:
docs/service/deployment.md(Docker build/run, node_hubintegration, env vars, port, scaling)
docs/service/operations.md(log format, /healthz, metrics,common errors and what they mean)
Acceptance:
docs/service/deployment.mdcovers: building, running, env vars(PORT, MAX_UPLOAD_MB, LOG_LEVEL, WORKER_POOL_SIZE, CORS), port
(8080), CORS configuration, Docker, node_hub, scaling notes.
docs/service/operations.mdcovers: structured log format, requestcorrelation IDs, /healthz semantics, suggested metrics (request
count, latency histogram, error rate, queue depth), top-5 common
errors and their fix.
only these two docs.
Depends on: P1 (architecture context).
Decomposed from easystitch#40