deployment

To configure an autoscale web service deployment, you set the deploymentTarget to autoscale and define the production run and build commands. This skill applies the configuration for web applications, APIs, and scheduled jobs.

Yes, you can fetch production runtime logs filtered by specific timestamp ranges and message regex patterns. The skill retrieves matching log entries and provides surrounding contextual line limits to investigate errors.

The best way to debug deployment issues is to fetch production runtime logs filtered by timestamps and regex patterns. This retrieves targeted error messages with contextual lines to analyze stack traces and diagnose runtime failures.

Yes, the deployment configuration supports static sites by setting the deploymentTarget to static and specifying a publicDir. It also handles run and build command arrays required for static site publishing.

After verifying app health and reviewing error logs, you can proceed with the publish workflow. The skill guides you to publish the production deployment while handling context limitations from task-agent or subrepl sessions.

Available deployment targets include autoscale, vm, scheduled, and static. You select the appropriate target based on your application type, whether it is a web service, API, bot, scheduled job, or static site.