Skip to main content
DeployConfig and its nested models define exactly what a deployment does.

Quick Start

1

API config

2

Cloud config


DeployConfig

Validation rules:
  • type="cloud" requires a cloud: section, otherwise raises ValueError("cloud config required for cloud deployment type").
  • type="api" fills in APIConfig() defaults when omitted.
  • type="docker" fills in DockerConfig() defaults when omitted.

Enums

DeployType

CloudProvider

"aws" · "azure" · "gcp"

ServiceState

running · stopped · pending · failed · not_found · unknown

APIConfig


DockerConfig

Sibling api: block (Docker only)

type: docker accepts an optional sibling api: block that configures the API server the container will run. Fields are the same as APIConfig above. Omitting the block runs the container with the same defaults as type: api — auth on, CORS on, port 8005.

Generated Gunicorn CMD

type: docker generates a Dockerfile whose CMD starts Gunicorn with fixed worker-timeout values tuned for agent LLM workloads.
These values are hard-coded in praisonai_deploy/docker.py (constant DEFAULT_GUNICORN_TIMEOUT). There is no YAML knob for them yet — if you need a different worker timeout, generate the Dockerfile with praisonai deploy plan and edit the CMD line before building.
The sibling api: block is type: docker-only. On type: cloud it is dropped — cloud providers shell out to external CLIs and never generate the API server.

CloudConfig


AgentConfig


Best Practices

For type="api" and type="docker", omit the nested block to accept sensible defaults. Only add fields you need to change.
provider, region, and service_name are required for cloud deployments and have no defaults.
cpu and memory are strings ("256", "512"), not integers — quote them in YAML.

Python API

Deploy class and result models

Quick Start

Minimal agents.yaml per type