Files
mev-beta/docker-compose.dev.yml
Administrator 803de231ba feat: create v2-prep branch with comprehensive planning
Restructured project for V2 refactor:

**Structure Changes:**
- Moved all V1 code to orig/ folder (preserved with git mv)
- Created docs/planning/ directory
- Added orig/README_V1.md explaining V1 preservation

**Planning Documents:**
- 00_V2_MASTER_PLAN.md: Complete architecture overview
  - Executive summary of critical V1 issues
  - High-level component architecture diagrams
  - 5-phase implementation roadmap
  - Success metrics and risk mitigation

- 07_TASK_BREAKDOWN.md: Atomic task breakdown
  - 99+ hours of detailed tasks
  - Every task < 2 hours (atomic)
  - Clear dependencies and success criteria
  - Organized by implementation phase

**V2 Key Improvements:**
- Per-exchange parsers (factory pattern)
- Multi-layer strict validation
- Multi-index pool cache
- Background validation pipeline
- Comprehensive observability

**Critical Issues Addressed:**
- Zero address tokens (strict validation + cache enrichment)
- Parsing accuracy (protocol-specific parsers)
- No audit trail (background validation channel)
- Inefficient lookups (multi-index cache)
- Stats disconnection (event-driven metrics)

Next Steps:
1. Review planning documents
2. Begin Phase 1: Foundation (P1-001 through P1-010)
3. Implement parsers in Phase 2
4. Build cache system in Phase 3
5. Add validation pipeline in Phase 4
6. Migrate and test in Phase 5

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-10 10:14:26 +01:00

60 lines
1.5 KiB
YAML

version: '3.8'
services:
mev-bot-dev:
build:
context: .
dockerfile: Dockerfile.dev
args:
# Set the git branch to build from (can be overridden via env var)
GIT_BRANCH: ${GIT_BRANCH:-master-dev}
image: mev-bot:dev-${GIT_BRANCH:-master-dev}
container_name: mev-bot-dev-${GIT_BRANCH:-master-dev}
restart: unless-stopped
volumes:
# Mount logs directory for persistent logs
- ./logs:/app/logs
# Mount data directory for database
- ./data:/app/data
# Mount development config
- ./config/config.dev.yaml:/app/config/config.yaml:ro
environment:
# Branch information
- GIT_BRANCH=${GIT_BRANCH:-master-dev}
- LOG_LEVEL=${LOG_LEVEL:-debug}
- ARBITRUM_RPC_ENDPOINT=${ARBITRUM_RPC_ENDPOINT:-https://arbitrum-rpc.publicnode.com}
- METRICS_ENABLED=${METRICS_ENABLED:-true}
env_file:
- .env
ports:
- "${PORT:-8080}:8080"
- "${METRICS_PORT:-9090}:9090"
command: ["start"]
# Health check to ensure the bot is running properly
healthcheck:
test: ["CMD-SHELL", "pgrep -f mev-bot || exit 1"]
interval: 30s
timeout: 10s
retries: 3
start_period: 40s
# Resource limits (adjust as needed for development)
deploy:
resources:
limits:
cpus: '4'
memory: 4G
reservations:
cpus: '1'
memory: 1G
labels:
- "dev.branch=${GIT_BRANCH:-master-dev}"
- "dev.environment=development"