How strangebeecorp/docker works
Project type and purpose
• This is a repository of Docker Compose “deployment profiles” for two cybersecurity tools: TheHive (an incident-response platform) and Cortex (an automated analysis engine).
• It provides ready-to-use stacks for a single‐host “testing” environment and two production tiers (prod1 and prod2), each split into a TheHive profile and a Cortex profile.
File structure
• Top-level directories:
• testing/
• prod1-thehive/ & prod1-cortex/
• prod2-thehive/ & prod2-cortex/
• docker-compose.yml (defines the containers and their networking)
• dot.env.template (environment variables for credentials, ports)
• certificates/ (TLS certs for NGINX)
• nginx/ (reverse proxy templates)
• elasticsearch/ (data & logs volume mounts)
• cassandra/ (only in TheHive profiles; data & logs)
• cortex/ or thehive/ (application config, logs, data directories)
• scripts/ (init.sh, backup.sh, generate_certs.sh, restore.sh, etc.)
README for additional insights
• This repo is purely orchestration: no app source code here, only manifests & helper scripts.
• It calls out the hardware requirements per environment and the steps required to initialize or upgrade (e.g., running init.sh).