mirror of
https://github.com/trailofbits/buttercup
synced 2026-06-21 14:11:39 +00:00
Riccardo Schirone
a8ed0ccbbe
* feat: Add simplified SigNoz integration using official Helm chart - Add SigNoz as a Helm dependency with conditional deployment - Enable SigNoz by default for minikube environments - Auto-configure OTEL to use internal SigNoz when enabled - Update Docker Compose to include existing SigNoz stack - Minimal configuration following the official chart approach Co-authored-by: Riccardo Schirone <ret2libc@users.noreply.github.com> * Configure local signoz * do not deploy signoz in ci * makefile: ensure signoz is available * feat: Simplify SigNoz integration for improved user experience - Remove external SigNoz configuration prompts from setup-local script - Make local SigNoz deployment the default for quickstart experience - Move external SigNoz configuration to MANUAL_SETUP.md for advanced users - Streamline README log access section to focus on local SigNoz UI - Relocate kubectl commands to QUICK_REFERENCE.md as alternative method - Improve documentation structure for better user onboarding Addresses feedback from @michaelbrownuc to simplify the integration before merging. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Riccardo Schirone <ret2libc@users.noreply.github.com> * Update MANUAL_SETUP.md --------- 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