docker-compose

/docker-compose — Docker Compose Generator

Generate a complete compose.yaml for an Alfresco Content Services stack.

Input

• ACS version from "$ARGUMENTS" or default to 26.1
• Read REQUIREMENTS.md for any deployment-specific requirements
• Resolve the Root path values from Section 2 (Project Architecture)

Output File

compose.yaml at project root.

Required Services

Core

• alfresco — ACS repository (with extension JAR mounted or built into image)
• postgres — PostgreSQL database
• activemq — Apache ActiveMQ message broker

Transform

• transform-core-aio — All-in-one Transform Service

Search (choose one based on requirements)

• elasticsearch — for Search Enterprise
• solr6 — for Solr-based search

Optional

• share — Share UI (if content model forms are needed)
• proxy — Nginx or similar reverse proxy
• content-app — Alfresco Content App (ACA)
• {extension-name} — Out-of-Process Spring Boot app (if /events command was used)

Conventions

• Use Docker Compose v2 format (no version: key)
• Every service must have a healthcheck
• Use condition: service_healthy in depends_on
• Use named volumes for persistent data
• compose.yaml always lives at the repository root, even in Mixed mode
• If a Platform JAR project is present, mount or copy its built artifact from the Platform JAR Root path
• If a Share JAR project is present, add a share service and use the Share project's Root path as the authoritative source for Share-tier resources
• If a Share JAR project is present, mount or copy src/main/resources/alfresco/web-extension/ and src/main/resources/alfresco/site-webscripts/ from the Share project into the Share container
• If an Aikau customization generates src/main/resources/META-INF/resources/, ensure those client-side resources are also copied into the Share image or otherwise made available to Share's webapp classpath/static resources
• If an Out-of-Process Spring Boot app is present, add it as a service that depends on activemq and alfresco with condition: service_healthy
• If an Out-of-Process Spring Boot app is present, its build: context must point to the Event Handler Root path from REQUIREMENTS.md (. for Event Handler only mode, {name}-events/ for Mixed mode)
• Never assume the Platform JAR, Share JAR, and Event Handler share the same build context or the same deployable artifact
• Never mount Share resources into the alfresco service, and never mount repository module resources into the share service
• Service start order — the alfresco service must depend on postgres, activemq, and transform-core-aio only. Never add solr6 or elasticsearch to alfresco's depends_on — Solr/OpenSearch discovers ACS after startup; making ACS wait for them creates a circular dependency (alfresco → solr6 → alfresco).