Files
langship.sh/docker-compose.yml
T
patel-lyzr 0284ff768a feat: enhance agent execution flow with multi-execution view and improved error handling
- Added multi-execution view to display multiple execution statuses.
- Improved error handling in agent triggering to surface failures.
- Updated execution view to support live updates via SSE and added a log panel for node logs.
- Enhanced pipeline canvas to display node statuses during execution.
- Introduced new fields in the build node form for Docker configurations.
- Updated API to support execution streaming and enhanced node catalog descriptions.
2026-05-13 22:15:08 +05:30

53 lines
1.5 KiB
YAML

services:
mongo:
image: mongo:7
ports:
- "27017:27017"
volumes:
- mongo-data:/data/db
restate:
image: docker.io/restatedev/restate:latest
ports:
- "8081:8080" # ingress
- "9070:9070" # admin
# NOTE: this stack reuses the buildkitd + registry from the sibling
# `langship` compose project — both already publish on
# 127.0.0.1:1234 (BuildKit) and 127.0.0.1:5000 (registry). Bringing them
# up here would collide on the same host ports. If you ever run flow
# standalone (without that other stack), uncomment the services in
# docker-compose.standalone.yml.
flow:
build: .
ports:
- "8090:8090" # JSON API
- "9080:9080" # restate callback endpoint
environment:
- FLOW_ADDR=:8090
- MONGO_URI=mongodb://mongo:27017
- MONGO_DB=flow
- FLOW_CORS_ORIGINS=http://localhost:3000,http://web:3000
- RESTATE_INGRESS_URL=http://restate:8080
- RESTATE_ADMIN_URL=http://restate:9070
- RESTATE_DEPLOYMENT_URI=http://flow:9080
- BUILDKIT_HOST=tcp://host.docker.internal:1234
depends_on:
- mongo
- restate
# buildkitd + registry are external (the sibling langship stack); see
# the note above. Add `external_links: ["langship-buildkitd:buildkitd",
# "langship-registry:registry"]` if you run flow as docker-compose and
# need network connectivity to those containers.
web:
build: ./web
ports:
- "3000:3000" # UI (open this in your browser)
depends_on:
- flow
volumes:
mongo-data: