tcb app

Targets framework applications that need a build step: detect the framework, build, upload the output, and bind routes. When the output is already static, upload it directly with tcb hosting in the same group.

Command index

Deployment

Command	Purpose
tcb app build	Build only, the output stays local
tcb app deploy	Detect the framework, build, and upload the output, creating the app on first deploy

Management

Command	Purpose
tcb app list	List apps
tcb app info	Show app details and the access domain
tcb app versions list	List published versions
tcb app versions detail	Show details of a specific version
tcb app delete	Delete an app

Static website hosting

Command	Purpose
tcb hosting deploy	Upload a file or directory to the static website, with optional verification, rollback, and remote cleanup
tcb hosting detail	Show the hosting status and access domain
tcb hosting list	List cloud files
tcb hosting delete	Delete a cloud file or directory

Notes

• tcb app deploy supports vite, next, static and other frameworks; override the build with --framework, --build-command, and --output-dir
• Both paths land on static hosting; the difference is whether the deploy builds first: tcb app deploy builds and uploads, while tcb hosting deploy only uploads
• Path syntax, enabling the service, and upload limits are covered in Paths and limits