CMI in Drupal 8 - Exporting and Importing of all the Drupal 8 site's configuration is made easy

Configuration Management Initiative (CMI) in drupal seperates “content” from "configurations". It uses yml files to store the configuration datas And it provides way for deploying configurations over the sites which includes development, staging and production.
CMI provides “Full Archive” and “Single Item” export and import of the configurations. "Full Archive" will generate a .tar file where that can be imported into the other one. "Single Item" will generate the code for a specific item. For Example - fields, field storage.
Inorder to import "configuration" between sites their UUID mush be identical. If you don't have a clonned instance you can change the UUID of the drupal instance.

[shiva]

Thanks man for ur video could please upload a video using drush how can we cex and cim in different environment.

[macksoneh]

I posed your video frequently to understand why you wanted to get UUID from drupaldev. It's not clearly explained in your video.
At 1:15 from a console, you did the following;
1. Get the UUID key from drupaldev
2. Update UUID key of drupalstage by applying the key from drupaldev
Why did you need to exchange UUID keys between drupaldev and drupalstage?
If you skip this process and do the rest from Drupal admin screen, what will happen?

[golubovicm]

If you select full "Full archive" what exactly is included and what not? I.e. If I create new content type, add some fields with it will it exported fully (all those new fields) or not?

[libortesar]

Is it possible to use it to make a copy of live site on local host and the update from local to live?