mirror of
https://github.com/trailofbits/buttercup
synced 2026-06-21 14:11:39 +00:00
f5a2a604ad
* Move docker compose files to dev/docker-compose/ directory - Moved compose.yaml, env.template, and env.dev.compose from root to dev/docker-compose/ - Updated all relative path references in compose.yaml to point back to root directory - Removed docker compose section from README.md - Added README.md in dev/docker-compose/ with usage instructions - Docker compose remains available for developers but is no longer prominently featured Addresses #181 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Riccardo Schirone <ret2libc@users.noreply.github.com> * Move env.dev.compose and env.template to dev/docker-compose/ directory - Restored env.dev.compose and env.template from git history - Moved both files to dev/docker-compose/ directory alongside compose.yaml - Files were previously deleted but should have been moved with other compose files - All references in compose.yaml and README.md are already correct 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Riccardo Schirone <ret2libc@users.noreply.github.com> * fix compose --------- Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: Riccardo Schirone <ret2libc@users.noreply.github.com>
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