Skip to main content

Eddy

Eddy is a template for maintaining a contributed Drupal module or theme on GitHub. Start your extension from it and you get CI on GitHub Actions, a local Drupal site to develop and test against, coding standards checks and mirroring of the code to Drupal.org.

You write the extension, and Eddy provides the rest. The commands that build the site on your machine are the same commands CI runs, so a run that passes locally is likely to pass in CI too.

Building a website?

Eddy isn't for building websites: use Vortex for that. The 2 templates do separate jobs, and a repository uses only 1 of them.

What you get​

  • ⚙️ CI on GitHub Actions - PHP 8.3, 8.4 and 8.5, and Drupal stable on 10, 11 and 12, plus legacy and canary tiers on 11 and 12. The version matrix explains the tiers. Code coverage comes from pcov, and goes to codecov.io when you add a CODECOV_TOKEN repository secret. With 1 override, the setup works with Drupal.org GitLab CI too.
  • 💻 Local development - a site built from drupal/recommended-project on the PHP of your host, by the same tooling commands that CI runs. You run them through make, Ahoy or directly. The build sets up a module or a theme and applies your patches. It also adds the development dependencies from composer.dev.json and the extensions you suggest.
  • 🧹 Coding standards - PHPCS with the Drupal, DrupalPractice, DrevOps and PHPCompatibility standards, PHPStan with PHPStan Drupal, Drupal Rector, Twig CS Fixer, ESLint, Stylelint, CSpell and Prettier.
  • 🧪 Tests - PHPUnit Unit, Kernel, Functional and FunctionalJavascript tests, in a local Chrome or a Selenium container, and JavaScript tests with Jest.
  • 🚚 Deployment - mirroring of the code and its tags to Drupal.org, or any other git remote, after CI passes, optionally to a different destination branch.
  • 🤖 Renovate - grouped pull requests that keep npm packages, GitHub Actions and Docker images up to date. It leaves Composer packages for you to update by hand.
  • 📝 Docs for your extension - README.md and CONTRIBUTING.md templates.

Eddy tests itself the way it tests a project created from it, and deploys to drevops/eddy_destination as a working example.

How it fits together​

Your repository holds the extension and a few configuration files. The commands that assemble, run and deploy it come from the drevops/eddy-tooling package, and both your machine and CI call them:

A quick look​

Installation covers every step, from the download to the first deployment. Each set of tabs on this site shows the commands for 1 setup: Make, Ahoy or no command wrapper. In a new, empty directory, the first run looks like this:

curl -fsSL https://eddy.drevops.com/install > install.php
php install.php   # Answer the questions about your extension
make build        # Assemble the codebase, start the server, install Drupal
make lint         # Check coding standards
make test         # Run the tests

Where to next​