3 Months, that’s a quarter of the year. What the hell, man?
- watch 1 drupalize.me/tutorial
- take notes
- painted the baseboard
- painted the shelved
- resuscitated my old PC
- installed free AV
- blew out the case
- hooked back up to internet with USB wifi card
- painted door & doorknobs to basement.
- inserted screen door
- cleaned garage
Last Night: Stix’d the entire frame and back/ sides of door, spray painted knobs and hinges. Paint & reassemble tonight..? let’s see 🙂
- 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.
- 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
- Configuration may be overridden on a particular environment through the
$configarray in a *.settings.php
- All feature/module default configurations are stored in YAML files that are dragged around as part of the config deployment.
- Config syncing (ie Stage>Prod) scenarios and solutions:
- Scenario 1: Configuration not managed at all.
- 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
- 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
- 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.
- If you’re working on a team…
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.
color coded exam requirements, so I know what I need to focus on.
I set up the Developer exam page, http://photograu.com/drupal-8-developer-exam-requirements/