Deployment Hooks
DevShop has many ways to allow customized actions after deployment of code and data.
Project Settings: Default Deploy Hooks
In the project settings form, you will see Default Deploy Hooks section with the following options:
Run database updates
Clear all caches
Revert all features
If you have the DevShop dotHooks module enabled, you will also see:
Run deploy commands in the .hooks file.
If you have the DevShop Acquia module enabled, you will also see:
Run Acquia Cloud Hooks.
You will also see a checkbox for "Allow environment-specific deploy hook configuration.".
Environment Settings: Deployment Hooks
In each Environment's Settings form, you will see a section called "Deployment Hooks" if "Allow environment-specific deploy hook configuration." was checked in the Project Settings form.
DevShop dotHooks
DevShop now supports placing your hook commands in a file called .hooks
, .hooks.yml
, or .hooks.yaml
.
Create a file with the format below to give your developers more control over what happens when new code is deployed.
System environment variables are available.
DevShop Aquia Cloud Hooks
DevShop now supports Acquia Cloud hooks. If your project is from Acquia, and you use the Cloud Hooks feature, you can now configure your project and environments to use them as deploy hooks when hosting sites in OpenDevShop.
To use DevShop Acquia Cloud Hooks integration:
Visit Admin > Hosting > Features.
Check "DevShop Acquia" under the "Experimental" category and submit the form.
Visit your project's settings page.
Under "Deploy Hooks", check the box for "Use Acquia Cloud Hooks" and submit the form.
Create your cloud hooks: Visit https://github.com/acquia/cloud-hooks.git for more information.
Last updated