ck:deploy

You can auto-detect the optimal hosting platform for deployment by using a tool that reads your project configuration files or docs/deployment.md to identify the target platform and execute the deployment workflow automatically.

Yes, you can deploy monorepos and static sites without manual platform selection by utilizing automated platform detection that evaluates your project structure and config files to recommend the most cost-optimized hosting environment.

The best way to keep deployment documentation updated is to use an automated deployment workflow that creates or updates your post-deploy docs synchronously, ensuring your deployment.md file reflects the latest hosting platform configuration.

No, automated deployment does not handle cloud infrastructure provisioning or credential management; it strictly focuses on platform detection, executing the deployment workflow, and synchronizing documentation updates.

You configure deployment instructions by creating a docs/deployment.md file or adding platform-specific configurations to your project files, which the automated deployment tool reads to identify and execute the appropriate hosting workflow.

Multi-platform deployment requires platform-specific reference files because the deployment tool uses them to coordinate distinct hosting workflows, ensuring the correct build and release steps are applied for the detected platform.