The official repository of on Drupal 7
davidrkupton Removes s3 (#1217)
* Removes the s3 module.
Latest commit 8a501d4 Nov 1, 2018
Failed to load latest commit information.
build Adds stash-db to on-demand test instances Jun 18, 2018
docker Lifts the custom ServerLimit from 6 to 10 (apache default=16). (#1176) Aug 13, 2018
dockerfiles Merge branch 'develop' into php-7-1-upgrade Aug 6, 2018
docroot Removes s3 (#1217) Nov 1, 2018
guides Updated documentation for gulp-image May 9, 2017
gulp-tasks Fix images Sep 24, 2017
hooks Remove post-db-copy git hook. Oct 31, 2018
libraries New repo, fresh code Oct 11, 2016
patches New repo, fresh code Oct 11, 2016
scripts Merge pull request #1116 from CityOfBoston/stash-restore-db Jun 18, 2018
tests Adds taxonomy term for procurement footer Mar 12, 2018
.dockerignore Adds a Dockerfile and docker-compose file Jan 24, 2018
.gitignore Separate the robots.txt files for each project Aug 11, 2017
.travis.yml Upgrade travis PHP version. Oct 10, 2018 Update Oct 28, 2016 Update Readme Oct 16, 2018
composer.json Revert "Implements drush 8." Aug 8, 2018
composer.lock Revert "Implements drush 8." Aug 8, 2018
docker-compose.yml Merge pull request #1107 from CityOfBoston/staging-cluster-support Jun 12, 2018
doit Addresses webconsole "AJAX" timeout. Provides new stash status to doi… Oct 30, 2018
gulpfile.js Fix images Sep 24, 2017 New repo, fresh code Oct 11, 2016 Created Mar 16, 2018
make.yml Update xmlsitemap 2.3 to 2.5. Sep 27, 2018
package-lock.json Update atob 1.1.3 to 2.1.0. Oct 10, 2018
package.json Update atob 1.1.3 to 2.1.0. Oct 10, 2018
project.yml New repo, fresh code Oct 11, 2016 Created pull request template Mar 16, 2018 New repo, fresh code Oct 11, 2016

City of Boston

The source code for, the official site of the City of Boston. is built on Drupal and serves as the digital front door for the City of Boston.

Welcome! We've released the code for in the public domain to engage developers and designers like you. We welcome your contributions to improve the City's digital front door, and are looking forward to sharing what we create together with the public.

— Mayor Martin J. Walsh

There’s a large, civic-minded ecosystem of software developers out there, especially in the Drupal community, and we’re hoping they’re willing to lend a hand and help grow, as well as foster collaboration between multiple organizations to solve common technical hurdles.


Get started with our developer guide.

Each contributor should fork the primary repo. All developers should then checkout a local copy of the develop branch to begin work.

For any work, pull requests must be created for individual tasks and submitted for review. Before submitting a pull request, be sure to sync the local branch with the upstream primary branch.

Pull requests should be submitted from the forked repo to the develop branch of the primary repo. Make sure to give your pull request a clear and descriptive title and use the template below.

Pull request template

## Changes

This PR references #[GitHub issue number]

 * [First change]
 * [Second change]
 * [Third change]

This PR references #[GitHub issue number]

Docker Quick-Start

Watch a YouTube video of this quick-start.

  1. Download Docker for Mac or Docker for Windows, or otherwise get a Docker environment with Docker Compose installed.
  2. Clone this repo.
  3. Run docker-compose up in the root directory. This will start the servers and stay open to show their logs.
  4. In another terminal window, initialize the database: docker exec bostongov_drupal_1 scripts/ (this will take 10+ minutes).
  5. Visit to see the blank install. Visit to log in, with admin/admin as username and password.

The Hub — our internal Drupal install — can run in the same container and against the same MySQL server. To initialize it, run:

docker exec bostongov_drupal_1 scripts/ hub

It’s available at and you can log in with admin/admin at

Since pulling files through the Docker volume mount is relatively slow, we keep vendored packages within the container and only map in our custom directories. So, only local edits to the following directories will be seen within the container:


You can modify this list by editing scripts/

Running drush commands

To get a shell within a running Drupal container, run docker exec -it bostongov_drupal_1 /bin/bash

From there you can run drush or commands.

Running tests in Docker

Assuming you have already done the local initialization, you can run:

docker exec bostongov_drupal_1 ./ -Dproject.build_db_from=initialize tests:all

Note: as of this writing, the tests do not work for the Hub environment (./

Running drush commands with Acquia cloud site alias

A drush alias is a shortcut to a remote Drupal site. It is in essence a tunnel through which drush commands can be issued. To use Drush to connect to Acquia Cloud site aliases, you must:

  1. Register SSH public keys for your Acquia user profile
  2. Download Drush aliases for all of your sites and extract the archive into $HOME.
  3. Ensure that your Acquia cloud site aliases are available with drush sa. You should see the aliases listed. If not, check that you exported the archive to your $HOME directory.

On-demand test instances

For City team members.

You can push your local repository up to a test instance on our staging cluster on AWS. This will let you show off functionality using data from a staging snapshot of


  • You will need Docker installed on your local machine
  • Install the AWS Command Line Interface
  • Get a “CLI” IAM user with an access key and secret key
  • Use aws configure to log your CLI user in locally. Use us-east-1 as the default region.


To create a place to upload your code, follow the instructions in the CityOfBoston/digital-terraform repo to make a “variant” of the staging deployment.

Pushing local code

To push your local repository up to the cluster, run:

$ ./doit stage <variant>

Where “<variant>” is the variant name you created in CityOfBoston/digital-terraform.

This will build a container image locally and upload it to ECR. It will then update your staging ECS service to use the new code.

By default, the container startup process will initialize its MySQL database with a snapshot of the staging environment from Acquia.

After the container starts up and is healthy, the doit script will print useful URLs and then quit.

Running drush on staging

Direct SSH access is not generally available on the ECS cluster. To run drush commands on your test instance, you can visit the webconsole.php page at its domain. This will give you a shell prompt where you can run e.g. drush uli to get a login link.

The webconsole.php shell starts in docroot.

Talk to another developer to get the username and password.

Preserving the database between pushes

By default, each time you deploy code to your test instance it starts with a fresh copy of the Drupal database.

If you want to preserve state between test runs, log in to webconsole.php and run:

$  ../doit stash-db

(The .. is because webconsole.php starts in the docroot.)

This will take a snapshot of your database and upload it to S3. The next time your test instance starts up, it will start its sync from this database rather than the Acquia staging one.

To clear the stash, so that your database starts fresh on the next test instance push, use webconsole.php to run:

$ ../doit stash-db reset

Public domain

This project is in the worldwide public domain. As stated in LICENSE:

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.

Staying organized

All projects, open source or not, need some way to stay organized. Whether reporting a bug (check out the template), suggesting a feature another template, filing a pull request yay, templates, or even just seeing what's next in the queue, here are some ways we keep things clear on the Digital Team:

Contribute to development

Check out our current prioroities for in our Git project.