Learn more about how to translate your Jovo project files like the
project.js and the Jovo Language Model into platform specific files like an Alexa Skill Interaction Model or a Dialogflow Agent with the
jovo build CLI command.
jovo build is the command to create and update the platform specific interaction models using the Jovo model. Using the files in the
/models folder and converting them into files in the
To learn more about Jovo Language Model, take a look Docs: Basic Concepts > Model.
jovo build command uses two elements of a Jovo project to create platform specific files:
- The platforms that are defined in the
- The Jovo Language Model files that can be found in the
This will prompt you if you want to overwrite the existing files or rather create a backup first. You can also skip this step and overwrite the files right away by using the
-p: If you want to update all your platforms, you can leave it out and it will update the ones listed in
project.js. If you want to update a specific platform folder you can pass the platform name as an argument:
-l: Specify the locale, which should be created/updated. Arguments:
de-DE, et cetera. Default: All files in the
-d: This is a shortcut to the
jovo deploy command. Deploy the platform files to their respective developer console.
-t: Used in combination with
--deploy to specify target of deployment. Arguments:
info (Skill Information),
model (Interaction Model),
-s: Used in combination with
--deploy. Path to source files. Default:
--stage: Specify the stage where the configuration will be taken from.
--ask-profile: Used in combination with
--deploy. Specifies which profile set up in ASK CLI should be used to deploy. Default:
--overwrite: Can be used together with the
--reverse command. This ignores the question if the existing files should really be overwritten.