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 Fletcher22 Nov 2023
Fatal error: Maximum execution time of 30 seconds exceeded in ...
When reloading a page, you may encounter the following error:Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/content/core/lib/Drupal/Core/{some file .php} on line n SolutionTo resolve this issue, you need to adjust the max_execution_time parameter in the php.ini...
Andrew Fletcher16 Nov 2023
Drupal and AWS - over 300 simultaneous database connections
The issue of over 300 simultaneous database connections in the context of AWS and Drupal can have several potential causes. Here are some common factors to consider:Server ConfigurationCheck your server configuration to ensure it can handle the expected number of simultaneous connections. This...