cloudrun-development

Deploy CloudBase Run backend services in Function or Container mode.

2|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lxb031018/qintu --skill cloudrun-development-lxb031018
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudrun-development
Source: https://github.com/lxb031018/qintu/tree/main/.codebuddy/skills/cloudrun-development
Command: npx skills add https://github.com/lxb031018/qintu --skill cloudrun-development-lxb031018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CloudBase Run Development helps you implement and deploy backend services that need long-lived connections, streaming or persistent endpoints, or custom runtimes without misconfiguring access, ports, or operational constraints.

Core Features & Use Cases

  • Mode Selection (Function vs Container): Choose the right CloudRun deployment model based on whether you need a Dockerfile/custom runtime or framework-style quick start.
  • Correct Runtime & Access Setup: Follow platform requirements like listening on PORT, keeping services stateless, and setting public/private access intentionally.
  • Tool-Driven Operations for an Agent-Ready Backend: Initialize, download, run (Function mode), deploy, inspect, and create Agent services using the correct query/manage operations and safer deployment sequence.

Quick Start

Use the cloudrun-development skill to deploy a long-lived WebSocket or SSE backend by specifying the absolute project path and explicitly selecting Function mode or Container mode before initializing and deploying.

Frequently Asked Questions about cloudrun-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a WebSocket or SSE backend on CloudBase Run?

To deploy a WebSocket or SSE backend on CloudBase Run, specify your absolute project path and explicitly select Function mode or Container mode before initializing and deploying the service.

What is the difference between Function mode and Container mode for CloudBase Run?

Function mode enables framework-style quick starts, whereas Container mode supports custom runtimes and Dockerfiles for deploying persistent HTTP or long-lived connection services on CloudBase Run.

Why does my CloudBase Run service fail to connect after deployment?

CloudBase Run deployment failures often occur when services do not listen on the platform-provided PORT, lack explicit public or private access configuration, or are not designed to be fully stateless.

Do I need a Dockerfile to deploy an Agent backend on CloudBase Run?

A Dockerfile is required for Container mode to utilize custom runtimes, but Agent backends can also be initialized and deployed using Function mode for framework-style quick starts without one.

Can I use CloudBase Run for persistent HTTP endpoints and streaming?

Yes, CloudBase Run supports persistent HTTP behavior, streaming, and long connections by applying correct port handling on the platform-provided PORT and maintaining a stateless service design.

What is the best way to inspect and debug a deployed CloudBase Run service?

The best way to inspect and debug a CloudBase Run service involves using tool routing via queryCloudRun and manageCloudRun operations to safely query, manage, and troubleshoot the deployed backend.