cirron deploy
Deploy your ML project to Cirron environments (PRODUCTION, DEVELOPMENT, CUSTOM) with automatic build, artifact upload, deployment monitoring, and rollback.Usage
Options
The command validates
cirron.yaml, ensures you’re authenticated, runs cirron build (unless --no-build), executes any beforeDeploy commands, uploads artifacts, monitors deployment with a 5-minute timeout, and finally runs afterDeploy commands. Production deployments require confirmation unless --force is passed.
Rollback
Rolls back to the most recent other successful deployment in the target environment.Examples
Configuration
cirron.yaml declares environments and optional pre/post-deploy hooks:
Monitoring and Artifacts
Statuses reported during deployment:pending → building → deploying → success (or failed).
build.outputDir and uploaded in batches of 5. The following files are filtered out automatically: .DS_Store, Thumbs.db, .git/, node_modules/, .env, *.log.
Troubleshooting
Best Practices and CI/CD
- Always test in staging before production. Use descriptive
--messagevalues for audit. - Use
beforeDeployfor validation,afterDeployfor notifications. - Keep a rollback strategy ready for production.
Related Commands
- cirron build - Build project before deployment
- cirron logs - View deployment logs
- cirron auth - Manage authentication
- cirron status - Check deployment status