Also, make sure you let us know which other UX/DX improvements you will like to see on the Drupal Console project.This is a command line interface (CLI), designed to generate standard code, interaction and debugging Drupal. įeel free to update Drupal Console to latest 1.7.0 and try this new feature while is hot and provide feedback. Installing Drupal 8 from configuration.Restoring a Drupal 8 site from Configuration Files.Using the Configuration Installer with Lightning.Read more about using config\_installer profile: Note that you will be using the config\_installer profile for any subsequent site installation, instead of the profile your site is currently using. Add the drupal/config_installer dependency using composer.Īfter following these steps you will be able to reinstall your site.Add patches to your composer.json file.Remove the install\_profile key from your settings.php file.Install the site using your preferred contrib or custom profile.Install the site using your new custom profile.Īfter following these steps, you will be able to reinstall your site using the custom profile and import the previously exported configuration. Add the config_suite module to your custom profile and have it as a dependency on your profile_ file.Add the drupal/config_suite dependency using composer.Yes, the other two well-known alternatives are: Note that you should replace ***development*** with the name you gave to your split. drupal config_split:import -split=development -no-interaction You should use the provided command to import the configuration and it will work as expected, without any issues or errors related to the uuid values. Yes, you can use the config_split provided Drupal Console command. Will this work with other modules like config_split? If you have any continuous integration or continuous deployment workflow you can integrate this command as part of that workflow. command:ĭescription: 'Build site by installing and importing configuration'Īfter adding this file, you can execute one command drupal build This is an example of a chain command to install a site and import a previously exported configuration. A chain command is a custom command that helps you automate multiple command execution, allowing you to define and read an external YAML file containing the definition name, options, and arguments of multiple commands and execute that list based on the sequence defined in the file.įor more information about chain commands, refer to the Drupal Console documentation. drupal self-update Can I automate the execution of the site installation and import configuration commands? Update per-site installation using composer: composer update drupal/console -with-dependencies drupal init -site -no-interaction What if my site is using an old version of Drupal Console? composer require drupal/console:~1.0 -prefer-dist -optimize-autoloaderĬreate a Drupal Console configuration file for your site. What if my site does not have Drupal Console installed?ĭownload Drupal Console using composer in your site. However, providing a better user experience while using Drupal 8 is one of the goals of Drupal Console and this is the reason we introduce features as the one we mentioned above. This functionality is not supported by Drupal Core out-of-the-box. Simple and easy right? Well, this is possible using Drupal Console starting with the 1.7.0 version. application:Įxecuting the commands to install the site and import your previously exported configuration: drupal site:install -force -no-interaction Updating your console/config.yml and append this configuration to the new overrides section. Installing a site from a previously exported configuration using Drupal Console is as simple as How to achieve this using Drupal Console? Developers will be able spin-up sites from scratch just by installing the site and importing configuration files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |