Staging: Deploy your Jovo Project to Different Environments

This page offers a selection of examples to learn how to deploy your Alexa Skill and Google Action to different environments. To learn more about the essentials of different stages, take a look at project.js Staging and config.js Staging

• Basic Setup
• Different Endpoints
• Different Platform Projects

Basic Setup

This is how your project.js could look like with three stages local, dev, and prod that use different endpoints (the Jovo webhook for local development and AWS Lambda for testing and production):

You now have two options to specify which stage is in use:

• Add a defaultStage and update it accordingly,
• Specify the stage in your environment variables, e.g. STAGE=dev.

You can add a defaultStage like this:

As the content inside the active stage is just merged into the other "stage-less" elements, there is no need to define a default stage for local, you can alternatively just define an endpoint and then override it for different stages:

You can then update the platform specific files by using the jovo build command:

Different Endpoints

The basic setup from above has one main problem: If you want to have both an Alexa Skill and a Google Action, you can't just use a Lambda ARN as an endpoint, you need to make it accessible with an API Gateways. This way you need to have different endpoints for both projects.

Here's how you can do it with a basic setup:

As the Jovo CLI uses ASK CLI to deploy to Lambda, it is sufficient for deployment if only the Alexa endpoint references the Lambda function, because this is the one passed to ASK CLI. For a little more structure, however, you can also use the newly introduced host object and define which askProfile to use to deploy it:

The above examples will add different endpoints to the /platforms folder project files by using the $ jovo build --stage <your-stage> command. To deploy the files to the right Lambda function, use $ jovo deploy --stage <your-stage>.

Different Platform Projects

You may also want to use different platform projects (e.g. Alexa Skill IDs and Google Action project IDs) for different stages. You can do this like so:

Again, the above examples will add different endpoints to the /platforms folder project files by using the $ jovo build --stage <your-stage> command. To deploy the files to the right Lambda function, use $ jovo deploy --stage <your-stage>.