Stats
Actions
Tags
From aiup-alfresco
Validates Docker Compose files for Alfresco deployments, ensuring every service has a healthcheck block and depends_on uses condition: service_healthy. Applies known healthcheck endpoints for common services.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aiup-alfresco:docker-compose-healthcheck-injectorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate and fix Docker Compose files for Alfresco deployments.
Validate and fix Docker Compose files for Alfresco deployments.
Verify these services are present (when applicable):
alfresco — ACS repositorypostgres — databaseactivemq — message brokertransform-core-aio or individual transform servicessearch — Solr or Elasticsearchshare — (optional, if Share UI is used)Every service must have a healthcheck block with:
test — appropriate health endpoint or commandinterval — recommended 30stimeout — recommended 10sretries — recommended 3start_period — recommended 60s for Alfresco, 30s for othersdepends_on must use condition: service_healthy (not just service name)alfresco depends on postgres and activemqshare depends on alfrescosearch depends on alfresco (for Solr) or is independent (Elasticsearch)curl -f http://localhost:8080/alfresco/api/-default-/public/alfresco/versions/1/probes/-ready-curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/share/ | grep -qE '^[23]'curl -sf -u $${ACTIVEMQ_USER:-admin}:$${ACTIVEMQ_PASSWORD:-admin} http://localhost:8161/admin/ > /dev/nullpg_isready -d alfresco -U alfrescocurl -f -H "X-Alfresco-Search-Secret: $${SOLR_ALFRESCO_SECRET}" http://localhost:8983/solr/alfresco/admin/pingcurl -s http://localhost:9200/_cluster/health | grep -q 'green\|yellow'curl -f http://localhost:8090/readyFLAG as ERROR any Share healthcheck that uses a path other than /share/:
| Bad pattern | Why it fails |
|---|---|
http://localhost:8080/share/page/home | /page/home does not exist in Share 26.x — Spring Surf throws a 500 Could not resolve view 'home'; the container stays health: starting forever and blocks dependent services (proxy) |
http://localhost:8080/share/page/dashboard | Same issue — page routes are user-session-dependent |
Correct pattern: accept any 2xx or 3xx from the Share root (it redirects to the login page):
test: ["CMD-SHELL", "curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/share/ | grep -qE '^[23]'"]
List all missing healthchecks and incorrect dependencies. Provide corrected YAML blocks.
npx claudepluginhub aborroy/aiup-alfrescoVerifies Docker health check configurations for PHP-FPM, Nginx, MySQL, PostgreSQL, Redis, and RabbitMQ. Detects improper intervals, missing start_periods, and recommends optimal parameters.
Provides 2025 Docker Compose production patterns: multi-environment overrides, env file strategies, non-root security, health checks, and version deprecation. Ideal for secure container deployments.
Generates Docker Compose configurations for multi-container apps with services, networks, volumes, health checks, dependencies, and environment setup. Useful for dev/prod orchestration.