How bento-platform/bento works
Project type and purpose
• Bento is a docker‑based, microservices platform (full‑stack) for building data‑focused portals (‑omics science).
• It provides a Python CLI (“bentoctl”) to configure, deploy and manage a suite of interoperable microservices via Docker Compose.
• The platform includes authentication, authorization, API gateway, data services (DRS, Beacon, CBioPortal, etc.), storage (MinIO), logging (Loki/Promtail), service registry, and front‑end/web components.
File structure
• Top‑level orchestrator:
– docker‑compose.yaml (and env‑specific overrides: dev, local, prod)
– py_bentoctl/ (the Python CLI and its helpers, entry point, configuration)
– etc/ (environment files, templates for each service, deployment scripts)
• lib/: a directory of individual microservice subfolders, each containing its own Docker Compose YAML and config templates:
• certs/, packs/, repos/ and continuous integration workflows under .github/workflows.
• docs/: a comprehensive set of markdown files detailing each aspect (installation, deployment, adding services, migration, monitoring, reverse proxy, etc.).
Key insights from the README
• Must use Docker ≥25.0 and Compose ≥2.25.0; Python ≥3.9 for bentoctl.
• The README emphasizes standardized APIs, microservice reuse, and CLI‑driven orchestration.