DevShop
Primary version
Primary version
  • Introduction
  • Introduction
    • About DevShop
    • Roadmap
    • Tour
    • How it works
  • Install & Upgrade
    • Installing DevShop
    • Upgrading DevShop
    • Changing Hostname
    • System Configuration with Ansible
    • Setup Examples
  • Using DevShop
    • Deployment Hooks
    • Migrating sites into DevShop
    • Customizing settings.php
    • Automated Testing
    • Acquia Cloud Hooks Integration
    • Remote Servers
    • Going Live
    • Scaling
    • Deleting Projects & Environments
    • Using SSL
    • Password Protection
    • Troubleshooting
  • Developing DevShop
    • Developing DevShop
  • Learning DevShop
    • The Complete DevShop Training
  • Contributing
    • How to contribute to DevShop
    • Release Process
Powered by GitBook
On this page
  • Project Settings: Default Deploy Hooks
  • Environment Settings: Deployment Hooks
  • DevShop dotHooks
  • DevShop Aquia Cloud Hooks
  1. Using DevShop

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.

# Fires after an environment is installed.
install: |
  drush {{alias}} vset site_name "Hooks Hooks Hooks"

# Fires after code is deployed. A "deployment" happens when you push to your
# git repository or select a new branch or tag for your environment.
deploy: |
  echo "Running hooks in the $DEVSHOP_ENVIRONMENT environment for the $DEVSHOP_PROJECT..."
  drush {{alias}} updb -y
  drush {{alias}} cc all
  echo "Environment Variables:"
  env

# Fires after "verify" task.
verify: |
  drush {{alias}} status

# Fires after "Run Tests" task.
test: |
  drush {{alias}} uli


# Fires after "Deploy Data (Sync)" task.
sync: |
  drush {{alias}} en devel -y

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:

  1. Visit Admin > Hosting > Features.

  2. Check "DevShop Acquia" under the "Experimental" category and submit the form.

  3. Visit your project's settings page.

  4. Under "Deploy Hooks", check the box for "Use Acquia Cloud Hooks" and submit the form.

PreviousSetup ExamplesNextMigrating sites into DevShop

Last updated 7 years ago

Create your cloud hooks: Visit for more information.

https://github.com/acquia/cloud-hooks.git