deployment

You can configure deployment targets using deployConfig, which supports autoscale, vm, scheduled, and static targets for websites, APIs, and bots across development, staging, and production environments.

To fetch production logs for debugging, use fetchDeploymentLogs with afterTimestamp and beforeTimestamp parameters, and apply message filtering to isolate specific runtime errors during deployment workflows.

Yes, this automates deployment configuration, publishing, and log debugging to streamline CI/CD release cycles, supporting incremental releases and rollback checks across various project types and environments.

Yes, deployConfig supports specifying run and build commands alongside publicDir, enabling static site publishing and custom build processes for different deployment targets and project types.

The best way to diagnose deployment failures is using fetchDeploymentLogs with timestamp filters and message matching to retrieve and analyze runtime logs from staging or production targets after publishing.