How target/strelka works
Project type and purpose
• Strelka is a container-based, microservice-oriented file-scanning platform.
• It provides CLI tools, a web UI, Go-based API/manager/front-end microservices, and a Python-based backend that runs a pluggable pipeline of file scanners.
Key architectural elements (from file tree & README)
• build/ + docker-compose/*.yaml → container definitions for each service
• configs/ → per-component YAML for Go services and Python backend (including Suricata & YARA rules)
• misc/envoy → an Envoy API gateway template
• src/go/cmd/… → Go binaries: strelka-frontend, strelka-manager, strelka-fileshot, strelka-filestream, strelka-oneshot
• src/go/api + src/python/strelka/proto → shared gRPC service definitions
• src/python/strelka → Python backend server, scanner modules, telemetry, config loaders
• misc/kubernetes → k8s manifests to deploy each container
Detail level
• Service container as its own component.
• Configuration mounts (configs/) feeding into services.
• Build artifacts (Docker images) in build/ → runtime containers.
• Don’t forget telemetry/traces and optional k8s overlays.