cloudrun-development

Deploying a stateless backend for SSE or WebSocket on CloudBase Run requires selecting Function or Container mode, listening on the injected PORT, and using manageCloudRun actions to execute the deployment flow at an absolute target path.

Function mode handles standard HTTP needs, whereas Container mode supports custom Dockerfile and runtime requirements. Selecting the correct mode ensures long-lived SSE or WebSocket connectivity and prevents broken access behavior during CloudBase Run deployment.

CloudBase Run services fail or lose connectivity when they do not listen on the injected PORT, use stateful designs, or use relative paths. Enforcing stateless backend design, externalizing durable data, and using absolute target paths prevents these deployment and runtime mistakes.

Yes, you can use a custom Dockerfile by selecting Container mode for your CloudBase Run deployment. Container mode accommodates custom runtime requirements while enforcing operational guardrails like listening on the injected PORT and maintaining stateless backend design.

To inspect and debug a CloudBase Run service, use the queryCloudRun action for read operations and manageCloudRun for write operations. Correct tool routing ensures safe inspection of your stateless backend without causing downtime or broken connectivity.

Creating an agent service on CloudBase Run involves deploying a stateless backend and using pointers to a dedicated Agent SDK. You must ensure correct port configuration and mode selection before deploying the agent service.