Deployment Steps

Deployment Steps are commands (Bash scripts) that you be executed to prepare the applications. Bunnyshell supports two type types of deployment steps: Pre Symlink and Post Symlink. They are executed in step 7 and step 8 of Application Deployment Process.

Pre Symlink Deployment Steps

All the commands in the Pre Symlink step are executed before making the new version live. Some of the commands that are usually executed in this step are :

  • installing dependencies

  • creating required directories

  • installing assets

  • adding application required permissions

  • running validation tests

Post Symlink Deployment Steps

All the commands in the Post Symlink step are executed after making the new version live. Some of the commands that are usually executed in this step are :

  • reload web servers

  • running validation tests

Adding a Deployment Step

From your Application View go to the Deployment Steps tab and click the on the add new action button. Search and choose a preexisting Deployment Step Template or click on the New Bash Script to start from scratch.

For a complete list of the Command Deployment Step check the following reference documentation:

Removing a Deployment Step

From the Deployment Step click on the right action button associated with the Deployment Step and click Remove.

Updating a Deployment Step

From the Deployment Step click on the right action button associated with the Deployment Step and click Update.

Enabling and Disabling a Deployment Step

From the Deployment Step click on the checkbox associated with the Deployment Step to enable and disable it. When an Application Deployment is run only enabled deployment steps are executed.

Running Deployment Steps only on specific Servers.

By default all actions are applied to all Servers that are attached to that Application. Your can select only specific servers to apply the Deployment Step on using the whitelist button at the bottom of the Deployment Step edit page.

Using Application Secrets in Deployment Steps

When a Deployment Step in run all Application Secrets are exposed as Environment Variables. You can use any secret by calling it like a Bash variable: ${secret_name}

Can I execute a command in a different language than Bash?

Bunnyshell noes not support this but you can provision your script with Automation Scripts and create a Deployment Step to execute that script. The result is is identical.

‚Äč