Public | Automated Build

Last pushed: 3 months ago
Short Description
Drupal web stack for bowline project
Full Description

Docker for Drupal development and testing


  1. Docker
    • Make sure you can successfully run docker commands without sudo. See Ubuntu example.
  2. Docker Compose

See also the wiki for platform-specific instructions.

Install Instructions

Use the following command to install bowline into your new or existing Drupal project directory.

wget '' -O ; cat ; read -n1 -p "Run above script? (y/n)" ; if [ "$REPLY" = "y" ]; then bash; fi


Activate bowline, adding the bowline environment to your bash session (The "dot space" is intentional, not a typo):

. bin/activate

This should add your project name to your bash prompt to indicate that your session has extra features. For example, ~/myproject (myproject) $.
Enter bowline to see a list commands available and the status of the containers. Note that the commands listed (such as drush) override any commands that were previously in your $PATH.

Docker subnet proxy for domain names as well as IP addresses

You may have noticed when running the bowline command that there is a section called "Proxy". As it suggests, run the following command to activate the proxy:


This will create and start an nginx container linked to a dnsmasq container. After they start it will add the web IP address and the project name to the dns container. The nginx proxy then uses that dns for finding your site and servers it as {projectname} (for example Once the proxy is active, bowline is aware of it when using the bowine or drush commands:

drush st

Important: the nginx proxy will not start if you have something else using port 80. You must either stop your other service (recommended) or edit the port in lib/proxy/fig.yml file to something other than 80.

Post-Install: Test and document your development sandbox

  1. Review which is indented to become your instructions for your development team. It will need to be modified to the specifics of your project.
  2. Replace the content of this file with appropriate description of your project.

Updating Bowline

The intention for typical usage of Bowline is to set up this repository as a secondary git remote. If you followed these instructions, the remote is called bowline. (You can add whatever is appropriate for your project as the origin remote.)

If you would like to pull in the latest Bowline code you basically just need to update the bin and lib directories.This can be done with the following command:

git checkout bowline/master -- bin lib

Then review the change and commit the update and push to your project.

Hoist Riggings

Bowline aims to be a general purpose tool while also allowing for any project specific needs. The hoist command helps to allow for many features yet keep simplicity for less involved projects. The word "hoist" is playing on the sailing term, suggesting that you would use the appropriate rigging depending on the direction you are heading.

Using Hoist

After activating, running the hoist command will output something similar to this:

Usage: hoist [rigging]
Available riggings:
behat  devtools  drupal-core-dev

So to "hoist" the behat rigging for your project you would do this:

hoist behat

Thus, you can easily install the pieces you need for your project. Each hoisting is logged in logs/rigging

Creating a Rigging

Riggings are simply a directory with a rigging_name.hoist bash script. A good example is the behat rigging. The behat.hoist script runs a composer command and copies a file to the bin directory, which may be typical processes of other possible riggings.


Pull requests welcome in typical GitHub fashion. If you would like to add a new feature to the project, consider using the hoist method described above.

Docker Pull Command
Source Repository