--- title: "Configure D10: CMS/Studio for Site Factory 2" date: "2024-03-26T21:27:09+00:00" summary: image: type: "article" url: "/site-factory/help/91661-configure-d10-cmsstudio-site-factory-2" id: "16fcd123-2ee7-416c-9f87-eacedb033c05" --- Table of contents will be added Goal ---- Install a Drupal 10 with Acquia CMS and Site Studio and prepare a codebase for Acquia Site Factory (ACSF) using Acquia Cloud IDE. Overview -------- This is Part 2 of a five-part comprehensive tutorial covering the set up of a new Drupal 10 codebase with Acquia CMS and Site Studio for Acquia Cloud Site Factory (ACSF). In this segment, you will install Acquia CMS and gain valuable insights into how to properly configure Site Studio to separate its configuration files and assets from the Drupal configuration files. This guide has been divided into five parts: 1. [Set up Cloud IDE, Install Drupal 10, and Prepare your Codebase for Site Factory](/tutorial/configure-drupal-10-codebase-acquia-cms-and-site-studio-site-factory-part-1) 2. **Acquia CMS and Site Studio installation and configuration for Site Factory** 3. [Create a Custom Profile and test New Site Creation with Site Factory](/tutorial/configure-drupal-10-codebase-acquia-cms-and-site-studio-site-factory-part-3) 4. [ACSF Deployment Workflow with Site Studio](/tutorial/configure-drupal-10-codebase-acquia-cms-and-site-studio-site-factory-part-4) 5. [Optional: Configure multiple Site Studio sync directories](/tutorial/configure-drupal-10-codebase-acquia-cms-and-site-studio-site-factory-part-5) In the following steps, I will guide you through the installation and configuration of Acquia CMS and Site Studio. 1. Install Acquia CMS using the Enterprise Low-Code Starter Kit ------------------------------------------------------------ [https://docs.acquia.com/acquia-cms/install-cms/](/node/55859) [https://docs.acquia.com/acquia-cms/enterprise-low-code-starter-kit/getting-started/](/node/56703) Run the **./vendor/bin/acms acms:install** command to begin the Acquia CMS installation using the Starter Kit wizard: ./vendor/bin/acms acms:install ![Codebase_2_Image1](https://acquia.widen.net/content/b597e8c7-3531-4497-9c2a-16da405d5124/web/66037_image1%20(1).png?w=1090&itok=wQ1-80xN) When prompted, use the Up and Down arrow keys to select “**acquia\_cms\_enterprise\_low\_code**” and press Enter. Do you want a demo with demo content?, **NO** Do you want to include the content model?, type **YES** and press **Enter**. Would you like to enable the Acquia DAM modules (configuration will need to be done manually later after site installation) ? \[no\]: **NO** Would you like to add GDPR functionality to the site (Yes/No) ? \[no\]: \> **NO** Please provide the Google Maps API Key: \> **(Press Enter)** Please provide the Site Studio API Key: \> **yoursitestudiokey-12345** Please provide the Site Studio Organization Key: \> **yoursitestudioorganizationkey-12345657a** Type **yes** and press Enter to the following prompt: You are about to: * DROP all tables in your 'drupal' database. Do you want to continue? (yes/no) [yes]: > yes Wait until the script installs Acquia CMS: ![Codebase_2_image20](https://acquia.widen.net/content/d2685917-2535-4b9b-a196-62e07f4c76cc/web/89430_image20.png?w=1090&itok=Y-bs78xw) Clear the cache: drush cr Login to the new installed Acquia CMS site: drush uli If you go to the homepage you should see the new Acquia CMS site: ![Acquia CMS dashboard with tabs for content management, showing membership duration of 5 minutes and 49 seconds.](https://acquia.widen.net/content/0ae27778-cd85-4973-88fe-87e416924848/web/url_d32b9d420af73e95504d5100c4169ae4.png) ### Disable the Site Studio Configuration Management module The **Site Studio Configuration Management** module offers a comprehensive out-of-the-box configuration, eliminating the need for manual setup. Additionally, it automates the export and import of Site Studio configuration with every configuration export/import Drush command (i.e drush cex or drush cim). Although it sounds great, it is essential for us to have the flexibility to execute the Drupal configuration export and import commands independently from the Site Studio package configuration export and import commands. Execute the following Drush command to disable the Site Studio Configuration Management module: drush pm:uninstall sitestudio_config_management ### Export the new Acquia CMS configuration Now that we have a fresh Drupal install using Acquia CMS, we need to export the current Drupal configuration so we can access the core.extension.yml file on a later step. Execute “drush cex” to export the configuration: drush cex Signorelli IDE:~/project (main *) $ drush cex [success] Configuration successfully exported to /home/ide/project/config/default. /home/ide/project/config/default Signorelli IDE:~/project (main *) $ 2. Configure the blt.yml file for Site Studio ------------------------------------------ Add the following code to the end if your blt/blt.yml file: site-studio: cohesion-import: true sync-import: false package-import: true rebuild: true 3. Site Studio Full Package Export configuration --------------------------------------------- [https://sitestudiodocs.acquia.com/7.4/user-guide/configure-full-package-export](/node/63896) You can export all of your Site Studio configuration as a single package file. Before you run a full package export you must define the export settings. This setting is used if you are using either the UI or drush to export your configuration. Navigate to the Site Studio “Full export settings” page (/admin/cohesion/sync/export\_settings), and make sure you have the following configuration. All the entity types should be checked making sure that the “Image styles” and “views” entity types are unchecked: ![Codebase_2_image41](https://acquia.widen.net/content/2a0d7425-77ac-44b8-abb4-744e279bc96f/web/de163_image41.png?w=1090&itok=Q5NMIwxY) ![Web interface showing export settings with options for image styles and views. A "Save configuration" button is highlighted.](https://acquia.widen.net/content/e481b9bc-6c28-4760-993d-d768b122403a/web/url_2ba4933d877dfa41617d8cb2301e0426.png) 4. Enable the ACSF, Config Split, and Config Filter modules -------------------------------------------------------- Enable the ACSF module: drush en acsf Signorelli IDE:~/project (main *) $ drush en acsf The following module(s) will be enabled: acsf, acsf_duplication, acsf_theme, acsf_variables Do you want to continue? (yes/no) [yes]: > yes [success] Successfully enabled: acsf, acsf_duplication, acsf_theme, acsf_variables Signorelli IDE:~/project (main *) $ Make sure the Config Split module is enabled: drush en config_split And make sure the Config Filter module is enabled as well: drush en config_filter 5. Site Studio Configuration Split ------------------------------- Navigate to “Configuration -> Development -> Configuration Split settings” (/admin/config/development/configuration/config-split) and click the “+Add Configuration Split setting” button. On the “Add configuration split setting” page, label the new configuration split as "**Site Studio**". In the "Static Settings" section, select "**Database**" as the storage type. Make sure to check the "**Active**" checkbox under the "Status" section. Lastly, enter "**cohesion\_\***" in the "Additional configuration" text area. Click the “Save” button to save the new configuration split: ![Website editing interface with fields for title, description, tags, and categories. Includes sections for news, content lists, and featured lists.](https://acquia.widen.net/content/abc5f7d4-f70f-4a17-b835-ba17005bfbcb/web/url_7a977736537582f02b0e2380012fad8a.png) 6. Config Ignore Configuration --------------------------- Navigate to “Configuration -> Development -> Configuration synchronization -> Ignore” (/admin/config/development/configuration/ignore). On the “Ignore” page, you should see the following configuration entities listed on the text area: * cohesion\_\* * language.entity.\* Add “cohesion.settings” to the list and click the “Save configuration” button to save the changes: ![Screenshot of a web configuration page titled "Ignore," showing options for ignoring specific configuration entity names, with a list and examples.](https://acquia.widen.net/content/3fa15606-fe19-465a-9c35-b22cf6a2f161/web/url_e1df8303dabfad0de42c3e740a2ed07d.png) 7. Export the modified Drupal and Site Studio configuration -------------------------------------------------------- Export the new Acquia CMS configuration: drush cex Signorelli IDE:~/project (master *) $ drush cex [notice] Differences of the active config to the export directory: +------------+---------------------------------------+-----------+ | Collection | Config | Operation | +------------+---------------------------------------+-----------+ | | acsf.settings | Create | | | config_split.config_split.site_studio | Create | | | core.extension | Update | | | user.role.content_editor | Update | | | user.role.content_author | Update | | | user.role.content_administrator | Update | | | config_ignore.settings | Update | +------------+---------------------------------------+-----------+ The .yml files in your export directory (/home/ide/project/config/default) will be deleted and replaced with the active config. (yes/no) [yes]: > yes [success] Configuration successfully exported to /home/ide/project/config/default. /home/ide/project/config/default Signorelli IDE:~/project (master *) $ Export the new Site Studio configuration: drush sitestudio:package:export Signorelli IDE:~/project (main *) $ drush sitestudio:package:export ➜ ➜ Exported 264 config and 38 non-config files. ➜ Signorelli IDE:~/project (main *) $ 8. Storing your Site Studio credentials outside of your codebase ------------------------------------------------------------- If you must store the Site Studio credentials outside of your codebase, you can create a **secrets.settings.php** file and then make its contents available to Drupal with a post-settings.php hook. By doing so, sensitive credentials are not kept in your database backups or your version control repository, allowing you to distribute database backups or grant repository access to team members who must not possess sensitive credentials. Visit the following Acquia documentation to get more information and instructions on how to store sensitive information outside of your codebase: **Storing sensitive information outside of your codebase** [https://docs.acquia.com/secrets](/node/55805) Congratulations on completing the second phase of the five-step guide! You have successfully navigated through the process of installing Acquia CMS and correctly configuring Site Studio to separate the Drupal configuration from the Site Studio configuration and assets. Now, let us move on to the next phase where you will learn how to create a custom Drupal installation profile for Acquia Cloud Site Factory. Next phase: [Create a Custom Profile and test New Site Creation with Site Factory](/tutorial/configure-drupal-10-codebase-acquia-cms-and-site-studio-site-factory-part-3)