cloudrun-development

To deploy WebSocket or SSE backend services on CloudBase Run, you need to configure a long-lived service endpoint with explicit PORT listening. This Skill guides you through the initialization and deployment sequencing for persistent streaming patterns.

Choose Container mode for CloudBase Run deployment when your project requires a custom runtime or a Dockerfile, and use Function mode for standard serverless execution. This Skill helps you select the correct model based on your runtime requirements.

You need a Dockerfile to deploy an AI agent service on CloudBase Run if you use Container mode for custom runtime environments. This Skill provides the deployment workflow for running agents as persistent Run services across both modes.

The best way to configure access control for a CloudBase Run backend is to specify PUBLIC, VPC-only, or mini-program internal access during initialization. This Skill sets the correct routing and access configuration based on your stated service requirements.

CloudBase Run services require explicit PORT listening and stateless design to ensure safe deployment sequencing and reliable scaling. This Skill enforces these requirements to properly manage persistent backend services without runtime conflicts.

To inspect and locally run a CloudBase Run service in Function mode, you use the local run and inspection workflow provided. This Skill supports initialization, local execution, and validation before you proceed to full deployment.