Deploy from CLI

Introduction

ozu-client isn't just a technical bridge to the Ozu API and Dashboard. It provides multiple tools to accelerate the development and deployment process, making it easier for developers to interact with Ozu's services, avoid reinventing the wheel, and streamline their workflow.

We always had the developer experience (DX) in mind when developing ozu-client.

Benefits of deploying from CLI

When making changes to your Ozu project's code, you'll have to re-sync your collections and settings configuration to Ozu Dashboard (using the ozu:configure command), then, usually, you'll want your recent changes to be deployed to production or any other environment, so you had to manually deploy your changes via the Ozu Dashboard by logging in and clicking on the "Deploy" button.

But instead of doing that, you can do:

php artisan ozu:deploy

1. It will ask for confirmation before deploying.
2. It will ask you if you want to sync (ozu:configure) your collections and settings configuration to Ozu Dashboard.

   CONTEXT

   We noticed that we frequently forgot to run ozu:configure after making changes to our project's code and before running a deployment. This method is intended to streamline the process inside one single command and avoid errors.

3. It will prompt you to choose the deployment target to deploy to.
4. It will ask for confirmation if there is unpublished content that would be published by this deployment.
5. It will trigger a deployment and you'll be able to see the deployment logs in real time.