mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Maxim
9fe2714d24
reskinnable-demo was cloned from examples/showcases/banking and vendors an identical Intelligence (durable-memory) docker stack — same seeded ids (jordan-beamson / morgan-fluxx / northwind-demo-user), same INTELLIGENCE_API_KEY and org. Both apps identified their backend purely by address, and both pointed at http://localhost:7050. So with banking's stack already up, a bare `pnpm dev` here (which, unlike run-demo.sh, checks no port bind) would silently attach to banking's backend and read/write the SAME memory buckets — worst case, the presenter reset button forgetting the neighbour demo's memories. Shift every published host port by +200 (705x/715x -> 725x/727x) in lockstep across compose, env, scripts, e2e config and tests so attaching to the wrong stack is impossible by accident: app-api 7050 -> 7250 gateway 7053 -> 7253 postgres 7156 -> 7256 redis 7158 -> 7258 minio API 7160 -> 7260 minio console 7161 -> 7261 bundled TEI 7167 -> 7267 The native Metal TEI on :7067 is left shared ON PURPOSE: it holds no demo state (buckets live in the now-isolated postgres/redis), the same TEI version + model yields byte-identical embeddings, and run-demo.sh reuses it when healthy rather than forcing a second ~20x-slower model load. A comment records why.