We are using drush make
in our deployment of new and updated platforms through Aegir and thus drush provision
.
We do not keep our theme css
and js
under version control as it complicates any conflict resolution between coffee
and scss
source files.
I want to automate the compiling of the css
and js
directories as part of the Create new platform provisioning script run by Aegir but cannot think of the right way to do this.
Main issues:
The granularity of a
drush-hook-post-make
is too course; not every download needs to be processed: e.g. only one theme needs to run a compile script after having been cloned from our git repo by drush make. How would we distinguish which downloads needed post-make processing?git pre-commit and post-checkout hooks are under vc in the theme's repo and would do the compiles but need to be explicitly invoked. Currently we manually symlink to the vc'd git hooks and run the compiles ... would like to automate this step.