5c887dee87
Why: baseline pending order edge handlers and runtime assets before security wave. What: add submit order contracts/handlers, service adapter updates, and docs/docker assets. Rule: keep technical intent and align repository workflow.
41 lines
1.1 KiB
Markdown
41 lines
1.1 KiB
Markdown
# Containerization Runbook
|
|
|
|
## Image Build
|
|
|
|
If the repo consumes internal packages from Gitea, pass feed credentials as build args.
|
|
|
|
```bash
|
|
docker build --build-arg NUGET_FEED_USERNAME=<gitea-login> --build-arg NUGET_FEED_TOKEN=<gitea-token> -t agilewebs/waiter-floor-bff:dev .
|
|
```
|
|
|
|
## Local Run
|
|
|
|
```bash
|
|
docker run --rm -p 8080:8080 --name waiter-floor-bff agilewebs/waiter-floor-bff:dev
|
|
```
|
|
|
|
## Health Probe
|
|
|
|
- Path: `/health`
|
|
- Fallback path: `/healthz`
|
|
- Port: `8080`
|
|
|
|
## Runtime Notes
|
|
|
|
- Exposes REST edge endpoints for waiter assignment and order submission flows.
|
|
|
|
## Health Endpoint Consistency
|
|
|
|
- Canonical probe: `/health`
|
|
- Compatibility probe: `/healthz`
|
|
- Container port: `8080`
|
|
|
|
## Demo Integration
|
|
|
|
- Participates in: **restaurant** demo compose stack.
|
|
- Integration artifact path: `greenfield/demo/restaurant/docker-compose.yml`
|
|
## Known Limitations
|
|
|
|
- Current runtime adapters are still predominantly in-memory for deterministic local/demo behavior.
|
|
- Demo PostgreSQL seeds validate integration contracts and smoke determinism, but do not yet imply full persistence implementation parity.
|