First off, thanks for the great work on drush!
Iam currently setting up a workflow for my new development environment in Aegir. This all works superbly combined with features and drush makefiles, iam provisioning all my sites exactly according to plan. The makefile is in git, with the normal dev/stage/live branches. Each branch has different git directives to pull different versions of proprietary modules and themes. So far so good.
But on my development server (which i run locally) I would like to create symlinks to my custom modules and themes instead of a download/git clone. This way during the development process I can have each build point to the latest working copy.
So in short:
- dev branch:
projects[moduleA][type] = 'module'
projects[moduleA][symlink][target] = /some/local/path/with/the/appropriate/permissions
- staging:
Clean git clone of the staging branch
- live:
clean git clone of the live branch
I've been trying to figure out if this is possible, but haven't found anything in the documentation. I can figure that this functionality is not suited for production environments so I was wondering if it is possible to extend the makefile vocabulary so to say via contributed modules.
Currently the only way I have found to hook into the makefile is to implement a custom project type. The attached file demonstrates how I solved it now. Be aware that it's just a proof of concept, but I would love some advise on how to make this a more robust plugin.
Comments
Comment #1
joostpluijmers commentedHmm... cant upload the drush_make_symlink.drush.inc. So I copy pasted it below.
Comment #2
greg.1.anderson commentedClosing support request due to lack of activity. Sorry no one was able to help you with your issue. Please re-open if you are still having trouble, or consider posting a question on Drupal Stack Exchange. If you have solved your problem, it would be helpful it you posted the resolution here to help others who may have the same problem in the future.