mirror of https://github.com/luxfi/bridge.git synced 2026-09-24 00:26:46 +00:00

Files

T

zeekay ee958f516f phase2-r2: scrub bridge3 / @luxbridge/app / lux-bridge references

Sweep through configs, docs, and ignore files after the structural
collapse in the previous commit. Updates fall into three buckets:

1) Restore the Dockerfile for app/bridge/
   - app/bridge/Dockerfile: new file, Vite SPA → ghcr.io/hanzoai/spa,
     same shape as the pre-collapse legacy Dockerfile, build context
     is repo root so @luxfi/bridge (workspace:*) resolves.
   - cmd/bridge/Dockerfile: switch UI-build stage to the workspace
     build context so the new app/bridge (which depends on the
     sibling pkg/bridge package) actually installs.
   - Makefile build-ui target: drop the per-app build context for
     the same reason — context must be repo root.

2) Update workspace docs to the new layout
   - README.md: rename @luxbridge/app row → @luxbridge/lux-tenant,
     port 3000 → 3001 (the slim tenant's vite config uses 3001).
   - docs/LLM.md: drop the bridge3 row, rename app/bridge row to
     @luxbridge/lux-tenant, update dev port.
   - docs/{BRIDGE-STATUS,LOCAL-SETUP,CI-CD-DOCKER-IMAGES}.md:
     `docker build … ./app/bridge` → `… -f app/bridge/Dockerfile .`
     so docs reflect the workspace-rooted build context.
   - .github/workflows/publish.yml: drop @luxbridge/app and
     @luxbridge/app-v3 from the private-packages comment.

3) Delete AI-slop status reports + test harness
   - CI_STATUS_REPORT.md, DEPLOYMENT_STATUS.md, WORKFLOW_AUDIT.md,
     WORKFLOWS_SUMMARY.md — stale and referenced bridge3.
   - test-bridge-ui.js — top-level Puppeteer/Playwright probe of the
     deleted legacy UI; not a workspace test.
   - .dockerignore: drop the test-bridge-ui.js entry now that the
     file no longer exists.

Out of scope (untouched): pkg/bridge/src/{Bridge,config,types,mount}
and pkg/bridge/src/app/ — Phase 3 R2 is working there. The
`@luxbridge/app` mentions in those files are historical comments
explaining the prior workspace cycle, not live references.

2026-05-21 15:15:37 -07:00

2.0 KiB

Raw Blame History

Lux Bridge MPC Integration - Current Status

✅ What's Running

MPC Nodes (Local)

node0: Running on http://localhost:8080 ✅
node1: Running on http://localhost:8081 ✅
node2: Running on http://localhost:8082 ✅
Status: All nodes are ready and accepting MPC requests

Infrastructure (Docker)

NATS: nats://localhost:4223 ✅
Consul: http://localhost:8501 ✅
PostgreSQL: localhost:5433 ✅

🚀 Next Steps

Option 1: Run Bridge Locally (Recommended for now)

Bridge Server:

cd app/server
pnpm install
pnpm dev

Bridge UI:

cd app/bridge
pnpm install  
pnpm dev

Option 2: Build and Use Docker Images

The compose files are configured to use ghcr.io/luxfi images, but they need to be built and pushed first:

# Build images (UI build context is repo root — pnpm workspace
# resolves @luxfi/bridge to the sibling pkg/bridge package).
docker build -t ghcr.io/luxfi/bridge-mpc:latest ./mpc-service
docker build -t ghcr.io/luxfi/bridge-server:latest ./app/server
docker build -t ghcr.io/luxfi/bridge-ui:latest -f app/bridge/Dockerfile .

# Push to registry (requires login)
docker push ghcr.io/luxfi/bridge-mpc:latest
docker push ghcr.io/luxfi/bridge-server:latest
docker push ghcr.io/luxfi/bridge-ui:latest

# Then run
make up

📝 Summary

The MPC integration is complete and functional:

✅ MPC nodes are running locally with the pre-built binaries
✅ All infrastructure services are running in Docker
✅ Configuration files use ghcr.io/luxfi images (ready for when images are published)
✅ Local development setup is working

🛠️ Useful Commands

# Check MPC nodes
ps aux | grep lux-mpc

# View MPC logs
tail -f logs/node*.log

# Check infrastructure
docker compose -f compose-infra.yml ps

# Stop infrastructure
docker compose -f compose-infra.yml down

# Stop MPC nodes
./stop-mpc-local.sh

The bridge is ready for development with secure multi-party computation!

2.0 KiB Raw Blame History