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 Fletcher10 Sep 2024
Resolving PHP GD library issues in Drupal
IntroductionFor a while now, one persistent issue has been bugging me: a warning on Drupal's 'status report' page that reads:GD librarylibrary bundled (2.1.0 compatible)Supported image file formats: GIF, PNG.Unsupported image file formats: JPEG, WEBP.Check the PHP GD installation documentation if...
Andrew Fletcher31 May 2024
Connecting AWS S3 with Docker for Drupal 10
Recently, I encountered an issue where my local Docker environment refused to connect to AWS S3, although everything worked seamlessly in AWS-managed environments. This challenge was not just a technical hurdle; it was a crucial bottleneck that needed resolution to ensure smooth Drupal deployments...