fix: docker run port mapping — map nginx port 80, not internal 9010

[eovidiu]

Summary

• Fix docker run examples in README.md, docs/getting-started.md, and docs/deployment.md to use -p 9010:80 instead of -p 9010:9010
• The Dockerfile serves the UI via nginx on port 80, while the Rust HTTP server binds to 127.0.0.1:9010 (internal only). The old mapping caused ERR_EMPTY_RESPONSE when accessing localhost:9010
• Docker-compose files are unaffected since they override CXDB_HTTP_BIND=0.0.0.0:9010

Test plan

• Verified docker run -p 9009:9009 -p 9010:80 -v $(pwd)/data:/data cxdb:latest serves the UI at http://localhost:9010 (HTTP 200)
• Verified API proxying works via curl http://localhost:9010/v1/contexts

[Copilot]

Pull request overview

Updates Docker run documentation to correctly publish the container’s nginx port (80) to the host’s expected UI/API port (9010), aligning the docs with the runtime networking model (nginx on :80 proxying to the internal Rust HTTP gateway on 127.0.0.1:9010).

Changes:

• Fix docker run examples to map -p 9010:80 (instead of -p 9010:9010) in docs and README.
• Clarify in getting-started docs that the UI + HTTP API are served via nginx on host :9010.
• Add a new .gitleaks.toml allowlisting two commits (not mentioned in PR description).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
docs/getting-started.md	Updates docker run port mapping and clarifies UI/API exposure via nginx.
docs/deployment.md	Fixes the Docker quick-start port mapping to publish nginx (:80).
README.md	Updates quick-start and local-image docker run examples to map 9010:80.
.gitleaks.toml	Adds a gitleaks allowlist for two commits (scope not described in PR).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This PR adds a new .gitleaks.toml with an allowlist for two specific commits, but the PR title/description only mentions Docker port-mapping documentation fixes. Please either (a) remove this file from the PR, or (b) update the PR description to explain why these commits must be allowlisted and confirm they do not contain unresolved secret findings (since allowlisting commits can mask real leaks going forward).