Deploy or Sync
To be able to check your changes on your site, you have to deploy those changes to your Instance.
This step describes two different methods. If this is your first go, we recommend to follow the process described in the "Deploying" section.
To deploy all changes, run the
pos-cli deploy [environment]
pos-cli deploy staging
A progress indicator shows that the deployment is in progress, and once it finishes, a "Deploy succeeded after is displayed.
We recommend to first deploy to staging, test, and only then trigger a deployment to production. In practice, deploy creates a zip file that contains all your files, and sends it to the API. It is then processed in the background. We store each zip file, so that you can roll back in case something goes wrong.
Learn more about our recommendations for version control and deployment on platformOS in the Development Workflow topic.
To immediately push changes in your codebase to the environment, run the
pos-cli sync [environment]
pos-cli sync staging
Using the sync command feels like working on localhost. It is recommended to use sync only for staging environments, as pushing changes immediately to production can be dangerous. Please note, that unlike deploy, this command will not delete resources when you delete the file.
After you have deployed your Instance, refresh your site in your browser. The home page has changed to include the text you added.
Read Effective Development Using pos-cli for more information.
Congratulations, you have finished our Hello, World! guide: You have set up your environment and learned how to change something on your site and deploy it.