Submitted by Darren on Wed, 22/09/2010 - 23:46
I've been using Drush Make for a while, and thought it would be useful to setup a Drupal Feature Server to host a few simple projects that I have been using in Makefiles. You can download the modules directly, or find the code on the project pages to include the modules in your Drush Make files. Alternatively, you can also download them directly using Drush (the Drupal command line tool) using the dl command. You just need to supply the following option
--source=http://www.darrenmothersele.com/fserver
I've removed the feature server. I'm not using it so much now I've moved to a more Git-centric workflow. The projects have either moved on to d.o or will be in the near future.
Hello!
I just started learning Drush Make and I found it difficult to understand how to update my custom features and modules which was installed by Drush Make.
I know that there are different download types in drush make: git, svn, etc. But I also see project 'location' property which stores fserver for updates.
You said: “I've moved to a more Git-centric workflow.”
Could you please explain how projects can be released by git, or maybe share some useful documentation about it.
Thanks!
Hi, thanks for the comment. I'm going to post a series of blog posts on development workflow. I'm working on the first one right now. This will cover setting up a development environment, using branching in Git, automating staging and deployment using Aegir. I'll hopefully get these up before the end of the year, but if you're interested you could start with mig5's excellent post on zero-touch Drupal deployment. He has an approach that uses Git, Drush and Aegir, but adds in Fabric and Jenkins Continuous Integration server into the mix. I have a slightly different approach that does away with the need for Jenkins and has everything running in one place. It's great for setting up on a small Linode server, for example.
Thank you for answer and link to mig5's workflow. I will follow your blog.