Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Define multi-container applications with proper dependency handling, networking, and volume management.
Define multi-container applications with proper dependency handling, networking, and volume management.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
depends_on: alone only waits for container start—service likely not ready yet Add healthcheck + condition for actual readiness: depends_on: db: condition: service_healthy Without healthcheck defined on target service, service_healthy fails
healthcheck: test: ["CMD", "pg_isready"] start_period: 30s start_period: initial grace period—health failures don't count during this time Slow-starting services (databases, Java apps) need adequate start_period Without it, container marked unhealthy before it finishes initializing
docker compose down preserves volumes docker compose down -v DELETES ALL VOLUMES—data loss -v often added by habit from tutorials—catastrophic in production Named volumes survive down; anonymous volumes deleted on down
deploy: resources: limits: memory: 512M Set limits during development—catches memory issues early Unlimited container can consume all host memory—kills other processes Copy limits to production config—don't discover limits in prod
Without it: node_modules, .git, secrets copied into image Mirrors .gitignore syntax—create at same level as Dockerfile Large build context = slow builds, large images, potential security issues At minimum: .git, node_modules, .env, *.log, build artifacts
docker-compose.yml: base config that works everywhere docker-compose.override.yml: auto-loaded, development-specific (mounts, ports) Production: docker compose -f docker-compose.yml -f docker-compose.prod.yml up Keep secrets and environment-specific config in override files, not base
services: mailhog: profiles: [dev] Services with profiles don't start by default—cleaner docker compose up Enable with --profile dev Use for: test databases, debug tools, mock services, admin interfaces
Shell environment (highest) .env file in compose directory env_file: directive environment: in compose file (lowest for that var) .env must be exactly .env—.env.local not auto-loaded Debug with docker compose config—shows resolved values
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.