5.1.0: Configurable config and configurable drush

Say hello to Flight Deck 5.1.0! This version includes some key updates and new features.

Bugfix: Updates to NodeJS

NodeJS, NPM, and libsass are now all on the same version as Alpine 3.13. This fixes a workaround in earlier builds where we relied on the versions provided by Alpine 3.12.

New feature: Configurable config

Earlier versions of Flight Deck assumed you would provide a configuration file in one of two possible locations:

/secrets/flight-deck-web.yml
/config/web/flight-deck-web.yml

Now, there are three different ways to provide config:

• Mount the configuration file at path /config/web/flightdeck-web.yml inside the container using a bind mount, configmap, or secret.
• Mount the config file anywhere in the container, and set the FLIGHTDECK_CONFIG_FILE environment variable to the path of the file.
• Encode the contents of flightdeck-web.yml as base64 and assign the result to the FLIGHTDECK_CONFIG environment variable.

The FLIGHTDECK_CONFIG variable allows Flight Deck to play nicer with testing services like Tugboat.qa.

Configurable Drush!

Previously, you had to use the drupal7 tag to get Drush 8.x, as required by Drupal 7. While we still provide that tag, it is no longer necessary. You can specify which version of Drush you need in config by setting the flightdeck_web.drush.version key:

---
flightdeck_web:
  drush:
    version: 8.x

Where:

• version is the Drush version series to use, either 8.x or 10.x.

Alternatively, you may choose to set the DRUSH_VERSION environment variable to 8.x. This is only respected on container startup. To force a particular command invocation to use Drush 8.x, use the drush8 command instead of drush. Likewise, you can use drush10 to call Drush 10.x.