Skip to main content

How to manage Drush8 configuration by YML files instead of DB upload

When We work on a large project with in a Team , then creating form fields, view or any configuration from in drupal 8 backend it stores in db, But when we need to push this fiend on staging server or production then it's very tipically to regenerate the field in staging environment or upload DB,

Drupal 8 Introduced the new concept for it, Config import and export based on YML files,
How to do it, Lets Look ...


With the help of drush we can convert all the config in YML files,
drush config-export
it will convert all the config in yml files in sites/default/files/config_*/

now push the YML files to staging through git or FTP , and use drush config-import in staging environment.

Simple Config Export & Import with Drush : 

Best way is to create a config directory parallel to drupal root, and set the setting to seetings.php like below,

$settings['config_sync_directory'] = 'config/sites/default';

These are the commands to export & import the config files,
drush config-export 
drush config-import

By using the config-split module:

By using the config-split we set the split setting & also specify the folder where the split config files will store, like store devel files which is split by setting,

folder : config/sites/default-split

And also add the active config-split setting in settings.php file,
on config split list(admin/config/development/configuration/config-split) machine name of the active settings like, local_multisite1
$config['config_split.config_split.local_multisite1']['status']= TRUE;

Export & import the config with config-split:

 drush config-split-export local_multisite1
drush config-split-import local_multisite1

 Ref: https://www.youtube.com/watch?v=QiuhRIPOJ5Y




Labels:
Location: Delhi, India

Comments

Post a Comment

Popular posts from this blog

Get The field values of node in Drupal 8

use Drupal \ node \ NodeInterface ; /** * Implements hook_ENTITY_TYPE_insert() for node entities. * * This tests saving a node on node insert. * * @see \Drupal\node\Tests\NodeSaveTest::testNodeSaveOnInsert() */ function node_test_node_insert ( NodeInterface $node ) { // Set the node title to the node ID and save. if ( $node - > getTitle ( ) == 'new' ) { $node - > setTitle ( 'Node ' . $node - > id ( ) ) ; $node - > setNewRevision ( FALSE ) ; $node - > save ( ) ; } } Now There is so many functions are there to get the values, For All the functions available visit the API code, https://api.drupal.org/api/drupal/core%21modules%21node%21src%21NodeInterface.php/interface/NodeInterface/8.2.x Some of as below, Node edit form, Drupal 8 Automatically Load the whole object no need to load the entity like below, if ($event->getFormId() == 'node_alexa_audio_clips_edit_form') { $node = \Drupal::ro...
Post a Comment
Read more

Dependency Injection in Drupal 8

Here are the important nuggets: DI is a design pattern used in programming. DI uses composition. DI achieves inversion of control. Dependency == service that your class needs == object of a certain type. Inject == provide == compose == assemble. Container == service container == dependency container. Instead of using  \Drupal::service('foo_service') , get the service from the  $container  if using a class. And the important reasons: Externalizing dependencies makes code easier to test. It allows dependencies to be replaced without interfering with other functionality. Retrieving dependencies from the container is better for performance. Services: node.grant_storage The easiest examples to find are services that have arguments, because you can search *.services.yml files for the word "arguments". In  node.services.yml  for example, there is this entry: node.grant_storage: class: Drupal\node\NodeGrantDatabaseStorage argument...
Post a Comment
Read more

Mysql Interview Questions

Current mysql version : 8 ( last was 5.7 ,  5.7 to directly 8 ) SHOW FULL PROCESSLIST is used to see all the query executing when refresh the site. 1 second == 1000 mili second, 0-500 ms responce time of any query is ok How to Read the MySQL Slow Query Log :   The MySQL slow query log is where the MySQL database server registers all queries that exceed a given threshold of execution time. This can often be a good starting place to see which queries are slowest and how often they are slow. MySQL on your server is configured to log all queries taking longer than 0.1 seconds. /var/log/mysql/mysql-slow.log Use EXPLAIN or EXPLAIN EXTENDED to explain the query how it is executed. MySQL  describe  or  ANALYZE  command shows the structure of the table. Best practice in respect of performance : 1 - always use index, 2 - index types , primary index and combined field index like fname & lname in one index not two index, 3 - one index sc...
Post a Comment
Read more