Readme

Meta

This document should be updated by YOU, as necessary as the project evolves. Add your author information for historical reference and professional context, as:

• Date first edited: NAME (email)

Authors:

• 2020-01-10: Calvin Tyndall (calvin@chapterthreellc.com)

Project Info:

• Working Repo: Github
• Hosting: Pantheon
• CI/CD: CircleCI -
• Backend: Drupal 8
• Frontend: Drupal 8 Theme - JCCBase subtheme(s).

Contents

• Local Development
  • Acquire a database dump.
  • Spin up the local.
• Module Management
  • Adding Contrib Modules
  • Updating Core
  • Updating Contrib Modules
  • Removing Contrib Modules
  • Applying Patches
• Git Workflow and Deploying Code
  • Parallel Workflow
  • Alternative Release Options
  • Testing and Approval
  • Automated Testing
  • Deploying Code
• Config Management
• Other Documentation
  • Parallel Git Worfklow on Pantheon

Local Development

• Docker: https://www.docker.com/community-edition
• Lando: https://docs.devwithlando.io

Lando/Docker optional, any *AMP environment will do, but there is helpful tooling here for Lando.

WARNING: Docker for Mac 2.2 currently breaks Lando. Use the Lando installer to install it's preferred version of Docker.

Once installed, cd to project directory and type lando for a list of commands.

Acquire a database dump.

Database can be fetched in multiple ways. I recommend saving to data/ directory which is ignored and within the environment so it can be saved for future resets and imported from there, without cluttering up the project root with different versions of the database.

[env] = live

• Terminus
  • Create new back up (optional) - terminus backup:create [project].[env] --element=db
  • Get latest backup - terminus backup:get [project].[env] --element=db --to=database.$env.sql.gz
• Drush Alias
  • lando drush @[alias] sql-dump --gzip > data/[alias]-YYYY-MM-DD.sql.gz
• Pantheon Dashboard
  • Select the environment tab or multisite
  • Select the Backups vertical tab
  • Download the latest database backup

You'll need access to the project. If not you'll need to ask for a database dump.

Spin up the local.

lando start - Spin up the environment. git checkout master - Start with a clean master to build your local.

Then get to a fresh state.

• lando db-import [path to db] - Import your database. Store db in data/.
• lando composer install - Composer install.
• lando th - "Theme: Help" for detailed info on managing multiple themes.
• lando reset - Runs updb, cim, cr ...

If composer install doesn't create settings.local.php and services.local.yml files in your sites/*/ directories find good examples in the examples directory. You can replace or alter these files in sites/*/ if you wish. They will not be replaced if they exist.

Make a new feature branch from master with your ticket id:

git checkout -b feature/TC-[id]--short-description

Ready to work.

Module Management

From the project root:

Adding Contrib Modules

• lando composer require drupal/[package_name] to add it to the composer.json.
• lando composer update drupal/[package_name] to update only the desired module.

Updating Core

• lando composer update drupal/core-recommended --with-all-dependencies

Sometimes composer will fail with a dependency issue. You can usually just add the dependency to the update list and try again. This list can get long if things are really out of date.

i.e. lando composer update drupal/core-recommended drupal/[dependency 1] symfony/[dependency 2] ... --with-dependencies

Updating Contrib Modules

• lando composer update drupal/[package_name] --with-dependencies

Sometimes several contrib modules are several versions behind.

Do not use lando composer update without specifying a module, or it will update everything that's outdated at once, possibly introducing regressions which you'll have to do much more testing for.

Updates should be controlled and tested well. It's easiest to do that in smaller chunks. Especially watch out for BETA, ALPHA, or DEV versions of modules which are not stable and make no guarantees about not breaking things between updates. Ideally, never use Alpha/Dev modules and use BETA's sparingly. Consider contributing to the project to help get it to a full release.

Removing Contrib Modules

Enabled modules should be removed from a code base in 2 separate releases. The first release update should simply uninstall the module. The second release should remove the module from the codebase as described below. If you do it all at once Drupal will not be able to find the module code on a test or production environment to be able to uninstall it, because it won't exist anymore.

Phase 1: Uninstall the module:

• lando drush @[alias] pmu [module] - uninstall the module.
• lando drush cex - export the config changes caused by uninstalling the module.
• Deploy the changes to update the Production site.

Phase 2: Remove the module:

• lando composer remove [package] will remove a package from require or require-dev, without running all updates.

Applying Patches

If you need to apply patches, you can do so with the composer-patches plugin.

To add a patch to drupal module foobar insert the patches section in the extra section of composer.json:

"extra": {
    "patches": {
        "drupal/foobar": {
            "Patch description": "Drupal URL to patch"
        }
    }
}

For patching robots.txt in Drupal 9, path such as trailing slashes might require different handling compare Drupal 8 else an error will occur during install/update. For example, a proposed patch that mentioned some Drupal URLs no longer requiring a trailing slash.

Git Workflow and Deploying Code

NOTE: Always reset your local to a production like state before starting a new feature. Configuration should be imported from master and/or a production database should be imported before starting work, so that config changes from the new feature are clean when exported.

This project is configured for a Parallel Git Workflow on Pantheon using multidev environments.

ENV -> GIT BRANCH

• develop (multidev) -> develop
• stage (multidev) -> stage
• Live (default pantheon live) -> master

In this way master is ALWAYS clean production code.

New feature branches for any work should be branched from master so it starts clean. If you branch from anything else, you will carry in code that's not related to your ticket that can be hard to separate for deployment to Production if your code is approved, but the other code is not. Your branch will be "contaminated". Stay clean to not accidentally introduce rejected code to production and to not frustrate whoever needs to deploy project code with precision.

feature/[ticket-id]--short-description or feature/TC-27--project-repo-base-theme

Lead commit messages with ticket id: TC-27: Message ...

This repo is managed on GitHub so push your feature there and make a Pull Request to develop. This will be merged and deployed to the develop (multidev) environment on Pantheon for INTERNAL QA.

If that passes, merge the clean FEATURE branch into stage for deployment to the stage (multidev) environment on Pantheon for CLIENT review/approval.

If it's approved for deployment to production, merge the clean FEATURE branch into master for deployment to the Live environment on Pantheon.

In this way, individual features can move through the environments without affecting, or being affected by, other work in progress. Issues can stall in any environment for any reason and not hold up the progress of any other issues in development. Hotfixes and security updates can breeze through without having to worry about whether or not you can deploy the 5 other things that might already have been sitting on stage for the last 3 months.

At the end of a sprint (or whenever it seems necessary) the develop and stage branches can be scrapped and started clean again by branching from master.

Alternative Release Options

• Single Feature/Hotfix: Deploy a single approved feature branch as a production release by merging it into the master branch.
• Release Branch: As features are approved on stage they can be merged into a new release-x.y.z branch that was cut from the clean master branch. Do not merge any un-approved feature branches into the release branch. Deploy the release branch whenever it's ready by merging it into the master branch.
• Completed Stage: You can consider stage a release branch if you're diligent in confirming all features merged into it are approved and signed off, then merging stage into master to deploy it as a release. This has some risk of deploying code that may have made it to stage but has not been signed off for release, so be careful.

Testing and Approval

A solo dev with limited oversight could be trusted to approve at the develop level, so the develop environment step may not be necessary. Leave it in place for when you need more detailed internal review. Just remember that stage and Live will get ahead of it if you don't use it for every feature, so you'll need to merge master into develop first, if you want a clean and concise Pull Request into develop.

Features should always be approved by the product owner on stage. Avoid doing internal QA on stage because if it fails, stage would be contaminated with a feature not ready for product owner review.

Though a solo dev may be trusted to deploy a feature or update without approval, requiring approval and signoff is recommended to help spot issues we may have blind spots for, and to protect us from breakage on production.

Automated Testing

• PHP linting on CI build_test
• PHP Code Sniffer on CI build_test
• PHP Code Sniffer on git pre-commit hook installed with composer.
• Cypress End to End and Visual Regression Tests run in a post deploy job.

Deploying Code

Merging a PR or pushing new commits to one of the environment branches on Github (epic-*, develop, stage, master), will trigger CircleCI to build, test and deploy the updated branch to it's corresponding environment.

It does this by syncing the production code from the working repo, to a separate production repo on the host.

After code syncs to the host, post deploy drush commands like updb -y, cim -y, cr are run. Make sure you check this for failure.

This process keeps working code separate from production code.

Configuration Management

This site uses config_split and config_exclude to keep environment-specific and developer modules out of the repository. See scripts/local/default/settings.local.php for example configuration.

Typical configuration workflow:

1. Import database locally. (See above)

2. Import configuration from code into database.

lando drush cim or drush cim

3. Make changes locally.

4. Export database configuration to code.

lando drush cex or drush cex

5. Commit and push changes.