Custom pipelines with .monkeyscloud.yml

Want to change build commands, deploy strategy, or health checks? Add a .monkeyscloud.yml file.

Updated Aug 4, 2026Deployments & CI/CD

By default, MonkeysCloud generates your pipeline from the detected stack. When you need more control, add a .monkeyscloud.yml file to the root of your repository.

A minimal example

version: 1

build:
  custom_steps:
    - name: "Security Audit"
      command: "composer audit"

deploy:
  strategy: rolling
  environments:
    production:
      branch: main
      replicas: 2
      require_approval: true

  health_check:
    path: /health
    interval: 10s
    timeout: 5s
    retries: 3

What you can configure

  • Stack override — force a stack instead of relying on auto-detection.
  • Build — runtime versions, custom install/build/test commands, extra pipeline steps, environment variables, and cache directories.
  • Deploy — strategy (rolling, blue_green, canary), auto-deploy branches, replica counts, and per-environment settings.
  • Health checks — path, interval, timeout, and retries.
  • Rollback — auto-rollback on failure and the error-rate threshold that triggers it.
  • AI — toggle automated PR reviews, deploy risk analysis, and build diagnostics.
  • Notifications — Slack, email, and custom webhooks.

Validation

Invalid configuration is rejected with a clear error before your pipeline starts, so a typo can’t take down a production deploy silently.

Custom pipelines with .monkeyscloud.yml