D8 Configuration workflow Notes

  1. D8 configuration is different, in that it is meant to capture the whole site from local>dev>stage>prod, instead of configuration changes captured in Features and encapsulated in individually importable modules, as in D7.
  2. That said, Features would still be employed for exporting a chunk o code / config for use in ANOTHER site, but once  the feature is imported, it all is a part of the site and managed though the core config management
  3. Configuration may be overridden on a particular environment through the $config array in a *.settings.php
  4. All feature/module default configurations are stored in YAML files that are dragged around as part of the config deployment.
  5. Config syncing (ie Stage>Prod) scenarios and solutions:
    1. Scenario 1: Configuration not managed at all.
    2. Scenario 2: Configuration sync directory in use, but sometimes configuration on the live site is edited: set up a local development instance, make and test your configuration changes there, export your configuration to files in your config sync directory, and finally use command-line tools like Git and Drush to deploy and import changes to the live site
    3. Scenario 3: Configuration changes are always made and tested on non-production instance(s) and then deployed to live: set up a strict workflow policy
    4. If you’re the one and only site admin and developer… learn how to use both GUI and command-line tools to manage and move your site’s configuration between instances.
    5. If you’re working on a team…

Configuration and Synchronization

The small thing that is a big thing that means Papa G needs to git his workflow in line:

5.2 Demonstrate the ability to use the Configuration and Synchronization options to import, export, compare configuration across environments.


  • Development Environments
  • Configuration Workflows
    •  Should be able to:
      • Change the configuration sync directory outside of web root
      • Clone a Drupal site
      • Export active configuration to YAML files
      • Move configuration from local – test – live

Tools to re-establish

  • Local Lamp stack
  • GitHub Repositories
  • GoDaddy deployment..?


yay! one thing green

today, I learned about D8’s core multilingual settings, thought it seems odd to me to go to the /en-gb/node/id URL alias in order to get at the translation for content.

For multilingual, you’ll need to enable the Drupal 8 Core Region/ Language Translate modules.

Nonzero… month?

So, how successful has my non zero initiative been? Well I certainly haven’t been posting about it as is evident here. That doesn’t mean I haven’t had any nonzero days. I’ve spend some time working on a table, I can spend some time working on a game system with Bennett, I’ve had some ideas sketching, but but I haven’t done any learning of Jubal skills at practice and site building at all, since the last time I posted here. I think I do need to make a habit of doing so, and as I can dictatedictated by voice, as I am doing now, then I should be able to at least make some silver progress report I’m on my commute to and from work so there won’t be a complete communication blackout between myself and myself. As myself is the only one reading this. But as I was saying I just need to push myself to make myself better because I’m not doing it on my own,

Acquia Certification Program Overview

The Acquia Certification Program Overview page has all of the certifications .

  1. Acquia Certified Site Builder – D8
  2. Acquia Certified Developer – D8
  3. Either: I can’t quite decide!  why not both?
    1. Acquia Certified Front End Specialist – D8
    2. Acquia Certified Back End Specialist – D8