Deploy with CloudShell and the Insites CLI
Last updated 18 November 2026Applies to Insites CLI 6.3
Take a project from your computer to staging and then production. You deploy with the Insites CLI and with CloudShell, check each release, and roll back a change you do not want.
You need the Insites CLI installed and an environment for each site. If you have not set these up, follow Set up your environment in the Getting Started course first. You need the Developer role or above on a site to deploy to it.
Step 1 of 7
Check your environments
From your project folder, list the environments the CLI knows about. Each one points at one site. The examples on this page use an environment called shane-sandbox-prod. Use your own environment names: your staging environment for the staging steps, and your production environment for the production step.
insites-cli env list[13:02:04] Available environments:
- [shane-sandbox-prod] private https://shane-sandbox.prod01-insites.ioCheck it worked: you see one line for each environment, with its stack and URL. If your staging or production environment is missing, add it with insites-cli env add, as the course shows.
All 7 steps done
You finished Deploy with CloudShell and the Insites CLI. Pick where to go next.