DevShop
component/docs
component/docs1.xPrimary version
component/docs
component/docs1.xPrimary 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
  • Acquia Cloud Hooks Integration
  • Hooks
  • post-code-deploy
  • post-code-update
  • post-db-copy
  • post-files-copy
  1. Using DevShop

Acquia Cloud Hooks Integration

PreviousAutomated TestingNextRemote Servers

Last updated 4 years ago

Acquia Cloud Hooks Integration

DevShop now supports firing Acquia Cloud Hooks when deploying to environments.

The code in acquia.drush.inc will detect an acquia repo and trigger your hooks to run.

See the Acquia Cloud Hooks repository for more information and samples:

Hooks

post-code-deploy

Changing branch or tag manually.

DevShop Equivalent: provision-devshop-deploy when triggered from front-end.

post-code-deploy site target-env source-branch deployed-tag repo-url repo-type

post-code-update

Deploying code to a branch environment automatically.

DevShop Equivalent: provision-devshop-deploy

post-code-deploy site target-env source-branch deployed-tag repo-url repo-type

post-db-copy

Triggered after Sync task.

post-db-copy site target-env db-name source-env

post-files-copy

Triggered after Sync task.

post-files-copy mysite prod dev
https://github.com/acquia/cloud-hooks