Skip to content

Deployment definition

sihil edited this page Jan 9, 2013 · 3 revisions

A deploy.json file is a hash that contains two keys:

  • packages
  • recipes

Packages

A package is defined by the following properties:

  • type
  • apps
  • data (optional)

Package types

Package types are the kinds of application that can be deployed by Magenta and have to be defined within the application.

Valid types are:

  • resin-webapp: A war deployed on the Resin appserver

Data definitions

  • waitseconds: the amount of time to wait for the application port to become available for connection after restart
  • checkseconds: the amount of time to allow for each check URL to return a 200 OK response
  • checkUrlReadTimeoutSeconds: the read timeout used whilst checking URLs

Recipes

Recipes define how actions depend on one another and what should be done for each package that is included in the recipe.

Each key in the recipe map becomes the name of the target action and can be referenced in both Riff-Raff and within the deployment definition itself.

Recipe properties

  • actionsPerHost (optional) : what actions should be carried out for each host the application is deployed to (e.g. .deploy)
  • depends (optional) : a list of recipe names that need to be executed before this task is carried out
Clone this wiki locally