Compose Anything

Compose Anything helps users quickly deploy various services by providing a set of high-quality Docker Compose configuration files. These configurations constrain resource usage, can be easily migrated to systems like K8S, and are easy to understand and modify.

Supported Services

Service	Version
Apache APISIX	3.13.0
Apache Cassandra	5.0.2
Apache Flink	1.20.0
Apache HBase	2.6
Apache HTTP Server	2.4.62
Apache Kafka	7.8.0
Apache Pulsar	4.0.7
Apache RocketMQ	5.3.1
Bifrost Gateway	1.2.15
Bolt.diy	latest
Budibase	3.23.0
Bytebot	edge
Clash	1.18.0
ClickHouse	24.11.1
Conductor	latest
Dify	0.18.2
DNSMasq	2.91
Dockge	1
Docker Registry	3.0.0
DuckDB	v1.1.3
Easy Dataset	1.5.1
Elasticsearch	8.16.1
etcd	3.6.0
Firecrawl	latest
frpc	0.64.0
frps	0.64.0
Gitea Runner	0.2.12
Gitea	1.24.6
GitLab Runner	17.10.1
GitLab	17.10.4-ce.0
GPUStack	v0.5.3
Grafana	12.1.1
Halo	2.21.9
Harbor	v2.12.0
HashiCorp Consul	1.20.3
IOPaint	latest
Jenkins	2.486-lts
JODConverter	latest
Kestra	latest-full
Kibana	8.16.1
Kodbox	1.62
Kong	3.8.0
Langflow	latest
Langfuse	3.115.0
LibreOffice	latest
LiteLLM	main-stable
Logstash	8.16.1
MariaDB Galera Cluster	11.7.2
Milvus Standalone Embed	2.6.2
Milvus Standalone	2.6.2
Minecraft Bedrock Server	latest
MinerU SGLang	2.2.2
MinerU vLLM	2.6.4
MinIO	RELEASE.2025-09-07T16-13-09Z
MLflow	v2.20.2
MongoDB ReplicaSet Single	8.0.13
MongoDB ReplicaSet	8.0.13
MongoDB Standalone	8.0.13
MySQL	9.4.0
n8n	1.114.0
Nacos	v3.1.0
NebulaGraph	v3.8.0
Neo4j	5.27.4
Nginx	1.29.1
Node Exporter	v1.8.2
OceanBase	4.3.3
Odoo	19.0
Ollama	0.12.0
Open WebUI	main
Open WebUI Rust	latest
OpenCoze	See Docs
OpenCut	latest
OpenList	latest
OpenSearch	2.19.0
PocketBase	0.30.0
Portainer	2.27.3-alpine
Portkey AI Gateway	latest
PostgreSQL	17.6
Prometheus	3.5.0
PyTorch	2.6.0
Qdrant	1.15.4
RabbitMQ	4.1.4
Ray	2.42.1
Redis Cluster	8.2.1
Redis	8.2.1
Restate Cluster	1.5.3
Restate	1.5.3
SearXNG	2025.1.20-1ce14ef99
Stable Diffusion WebUI	latest
Stirling-PDF	latest
Temporal	1.24.2
TiDB	v8.5.0
TiKV	v8.5.0
Valkey Cluster	8.0
Valkey	8.0
Verdaccio	6.1.2
vLLM	v0.8.0
Windmill	main
ZooKeeper	3.9.3

MCP Servers

Server	Version
API Gateway	latest
ArXiv MCP Server	latest
Basic Memory	latest
ClickHouse	latest
Docker	latest
Dockerhub	latest
E2B	latest
ElevenLabs	latest
Fetch	latest
Firecrawl	latest
Filesystem	latest
Grafana	latest
Markdownify	latest
Markitdown	latest
Memory	latest
MongoDB	latest
Neo4j Cypher	latest
Neo4j Memory	latest
Notion	latest
OpenAPI Schema	latest
OpenAPI	latest
OpenWeather	latest
Paper Search	latest
Playwright	latest
Redis MCP	latest
Rust Filesystem	latest
Sequential Thinking	latest
SQLite	latest
Tavily	latest
Text to GraphQL	latest
Time	latest
Wolfram Alpha	latest
YouTube Transcript	latest

Guidelines

1. Out-of-the-box
   • Configurations should work out-of-the-box with no extra steps (at most, provide a .env file).
2. Simple commands
   • Each project ships a single docker-compose.yaml file.
   • Command complexity should not exceed docker compose up -d; if more is needed, provide a Makefile.
   • For initialization, prefer healthcheck with depends_on using condition: service_healthy to orchestrate startup order.
3. Stable versions
   • Pin to the latest stable version instead of latest.
   • Expose image versions via environment variables (e.g., FOO_VERSION).
4. Configuration conventions
   • Prefer environment variables over complex CLI flags;
   • Pass secrets via env vars or mounted files, never hardcode;
   • Provide sensible defaults to enable zero-config startup;
   • A commented .env.example is required;
   • Env var naming: UPPER_SNAKE_CASE with service prefix (e.g., POSTGRES_*); use *_PORT_OVERRIDE for host port overrides.
5. Profiles
   • Use Profiles for optional components/dependencies;
   • Recommended names: gpu (acceleration), metrics (observability/exporters), dev (dev-only features).
6. Cross-platform & architectures
   • Where images support it, ensure Debian 12+/Ubuntu 22.04+, Windows 10+, macOS 12+ work;
   • Support x86-64 and ARM64 as consistently as possible;
   • Avoid Linux-only host paths like /etc/localtime and /etc/timezone; prefer TZ env var for time zone.
7. Volumes & mounts
   • Prefer relative paths for configuration to improve portability;
   • Prefer named volumes for data directories to avoid permission/compat issues of host paths;
   • If host paths are necessary, provide a top-level directory variable (e.g., DATA_DIR).
8. Resources & logging
   • Always limit CPU and memory to prevent resource exhaustion;
   • For GPU services, enable a single GPU by default via deploy.resources.reservations.devices (maps to device requests) or gpus where applicable;
   • Limit logs (json-file driver: max-size/max-file).
9. Healthchecks
   • Every service should define a healthcheck with suitable interval, timeout, retries, and start_period;
   • Use depends_on.condition: service_healthy for dependency chains.
10. Security baseline (apply when possible)
    • Run as non-root (expose PUID/PGID or set user: "1000:1000");
    • Read-only root filesystem (read_only: true), use tmpfs/writable mounts for required paths;
    • Least privilege: cap_drop: ["ALL"], add back only what’s needed via cap_add;
    • Avoid container_name (hurts scaling and reusable network aliases);
    • If exposing Docker socket or other high-risk mounts, clearly document risks and alternatives.
11. Documentation & discoverability
    • Provide clear docs and examples (include admin/initialization notes, and security/license notes when relevant);
    • Keep docs LLM-friendly;
    • List primary env vars and default ports in the README, and link to README.md / README.zh.md.

License

MIT License.