Skip to main content

Assuming there is a new field requiring a change on a content type. How do you ensure the changes apply in the next deployment?

There are a couple of ways to achieve this... depending on whether a custom module exists or not.  I'll focus on using Drush.

Drush is a great tool to manage many of Drupal's features.  For changes that are applied within the backend, best to use Drush export command - drush cex.  Then your config directory at root will be updated with the change.  So when you git add/commit/push, whether via lando or any other plugin or not, the next environment has the change ready to be applied.  Write into your pipeline for drush cim (Drush import to occur).  These actions will ensure the changes are applied in the next deployment.

Related articles

Andrew Fletcher25 Sep 2022

Adding Tailwind css to Drupal

Tailwind CSS is a highly customisable framework that delivers developers the tools to quickly pull your site together.   Initial Configuration The installation and configuration steps are essentially the same as those outlined within the Tailwind documentation. Note they need to be...
Andrew Fletcher07 Sep 2022

common Drush commands

If your Composer project doesn't have Drush listed as a dependency, you can install Drush from command line as follows: composer require drush/drush To check your version of Drush, use drush --version   Status check drush status Will output something similar to ...