Docker Demo
The Docker Demo is for a first technical evaluation. It does not need a real model key and never connects to your production system.
Components
Section titled “Components”| Service | Role |
|---|---|
bailinghub |
Console, Client API, routing, tool governance, approvals, and traces |
mysql |
Configuration, jobs, messages, approvals, and audit state |
demo-business |
Orders, support tickets, refund approval, and failure probes |
demo-agent |
Deterministic in-hub target that exercises the real tool runtime |
export BAILING_TOKEN="${BAILING_TOKEN:-$(openssl rand -hex 32)}"docker compose up --buildOn a fresh Ubuntu/Debian host:
curl -fsSL https://www.bailinghub.com/install.sh | shUse BAILING_INSTALL_MODE=source only when you explicitly want a source build.
Open the console at http://localhost:18900/console/, Demo Business at http://localhost:19080/, and health endpoint at http://localhost:18900/health.
The local Compose default is admin / bailing-demo-admin. The installer generates and prints its own password and never overwrites an existing .env.
Demo tools
Section titled “Demo tools”| Tool | Meaning | Governance |
|---|---|---|
list_demo_orders |
Read orders | Read-only, trusted subject required |
create_demo_ticket |
Create support ticket | Medium-risk write, trusted subject required |
request_demo_refund |
Request refund | High-risk write, approval required |
demo_failure_probe |
Return a fixed business 5xx | Failure-trace demonstration |
Run the 10-minute path, then submit a refund request and decide it in Demo Business. The setup wizard can also import an owned demo dataset: import creates configuration only; smoke execution creates real jobs and traces.
docker compose exec bailinghub npm run smokedocker compose exec bailinghub npm run demo:e2eFor image selection, dataset ownership, and network troubleshooting, read the fixed v0.9.0 Demo guide.