mirror of
https://github.com/trailofbits/buttercup
synced 2026-06-21 14:11:39 +00:00
Dan Guido
1c574962b3
* fix: standardize packaging configuration across components - Fix fuzzer package name from 'fuzzing-infra' to 'fuzzer' for consistency - Add missing README field to common/pyproject.toml - Standardize seed-gen script naming to follow buttercup-* convention - Remove redundant flake8 dependency from orchestrator and patcher (ruff handles linting) - Update lock files to reflect dependency changes - Auto-format code in common and seed-gen components * refactor: standardize dev dependencies across all components - Add pytest-cov to all components for consistent test coverage reporting - Standardize types-redis version to 4.6.0 across all components - Standardize types-requests version to 2.32.0 where used - Remove unused pytest-asyncio from orchestrator and patcher (no async tests found) - Remove unused types-python-dateutil from patcher (only used in orchestrator) - Keep component-specific dependencies where justified: - orchestrator: pytest-xdist for parallel testing, API testing tools - patcher: pytest-xdist for parallel testing - common: types-PyYAML, dirty-equals for testing - seed-gen: tqdm for progress bars All components now have consistent base dev dependencies with optional extras as needed. This improves maintainability and reduces confusion. * fix: update deployment configs for renamed seed-gen command - Update docker-compose to use buttercup-seed-gen command - Update Kubernetes/Helm deployment to use buttercup-seed-gen command - These are critical fixes to ensure deployments work with the renamed command
Docker Compose Development Setup
This directory contains the legacy Docker Compose setup for Buttercup CRS, preserved for developers who need to run specific components for quick testing and development.
Usage
From the repository root directory:
# Run all services
cd dev/docker-compose && docker-compose up -d
# Run specific services or profiles
cd dev/docker-compose && docker-compose --profile fuzzer-test up -d
cd dev/docker-compose && docker-compose --profile graphdb up -d
# Stop services
cd dev/docker-compose && docker-compose down
Configuration
env.template- Template for environment variables (copy to.envand customize)env.dev.compose- Development-specific environment configurationcompose.yaml- Main compose file with all services
Notes
- This setup is not recommended for production - use the Kubernetes deployment instead
- Primarily useful for developers who need to run individual components for testing
- The main deployment method is now Kubernetes via
make deploy-localfrom the repository root - See the main README for the recommended setup instructions