![]() ![]() This approach saves effort for everyone when a site needs a new landing page. This gives our sites a robust experience to construct pages with the components where our clients want. We typically work around this using multiple configuration directories for each environment (I’ll illustrate how that worked in a moment).Īt Bounteous, we take a component-based approach to building many reusable content elements for sites. Moving configuration between environments would cause undesired changes to staging and (ultimately) production environments. On a recent project, I ran into a few situations where the off-the-shelf Drupal 8 configuration approach was too heavy-handed for us. Life is definitely easier in Drupal 8! The Problem You can then commit and merge configuration changes in source code control, deploy the configuration, then import it in to the destination environment. In Drupal 8 Core, configuration for most site settings and definition of structural pieces of the site can be exported with one click of a button or a single drush command. This worked well enough, but it wasn’t quite as effortless as it could be.ĭrupal 8’s configuration system is miles ahead of Drupal 7. This left the task of moving configuration to other environments to contributed modules like Features. In Drupal 7, configuration and content are both stored in the database. For example, if you make a new View page in the development environment and want to deploy it to the testing environment, it’s a matter of exporting the configuration, committing it to version control (git), and deploying/importing it on the other environment. This makes the process of moving configuration settings from one environment to another much easier than in previous versions of Drupal. What is Drupal 8 Configuration Management?Ĭonfiguration Management is a new Drupal core system that allows database configuration to be exported to YML files. Having attended DrupalCon in Nashville this year, I was inspired to write a post about my experiences with this and share how a Drupal developer can devise a comprehensive approach to managing Drupal 8 configuration across multiple environments. In 2018, there were 241,000 Drupal 8 sites up from 159,000 Drupal 8 sites in 2017, representing a 51 percent increase year over year, according to Dries Buytaert. Java is a registered trademark of Oracle and/or its affiliates.The rise in Drupal 8 installations has brought with it an increased need for environment-based Drupal configurations. For details, see the Google Developers Site Policies. Site Status monitoring included in Drupal 9 Core.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. SmartDocs Parameters (smartdocs_parameter)Ī login (apigee_account)Īpigee Site Status Checklist (apigee_checklist) SmartDocs Attachments (smartdocs_attachment) For Drupal 9, the Kickstart distribution handles site configuration using Drupal configuration management.ĭevConnect blog content types (devconnect_blog_content_types)ĭevconnect Content Creation Menu (devconnect_content_creation_menu)ĭevconnect Default Structure (devconnect_default_structure)ĭevconnect Homepage (devconnect_homepage) The Developer Portal - Profile category of modules are used for the initial configuration of the D7Pĭistribution. ![]() You can call the Apigee APIĭirectly or open an enhancement ticket on if neededĭevConnect Limit API Product by Role (devconnect_apiproduct_access)Įnable the "Apigee Edge API product RBAC" submodule.ĭevConnect Monetization (devconnect_monetization)ĭevConnect Monetization Base Recurring Payment (devconnect_mint_payment)Ĭustom code is required to configure a recurring Commerce payment provider.ĭevConnect Monetization Payment (devconnect_monetization_payment)Įnable the "Apigee Monetization Add Credit" submodule.ĭevConnect Monetization Recurring Payment Worldpay (devconnect_mint_worldpay)Īny Drupal Commerce 2.x payment gateway may be used. ![]() Key-Value map calls to the Edge API are not part of the Drupal 9 Edge module. Set admin email notifications for new users by Configuring user account settings.ĭevConnect App Attribute Management (devconnect_app_attributes)Įnable the "Apigee Edge Debug" submodule.ĭevConnect Key-Value Maps (devconnect_key_value_map) Status checks are handled by the Update Manager in Drupal 9 Core.ĭevconnect Admin notification (devconnect_admin_notify) The following table outlines feature correspondence between the modules available for the Drupalħ Developer Portal (D7P) and the Drupal 9 Developer Portal: Drupal 7 ModuleĭevConnect developer apps (devconnect_developer_apps)ĭev Portal Status Report (devconnect_status) You're viewing Apigee Edge documentation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |