One important distinction is that it is okay to have Components that let an editor select from a list of blocks when creating actual content-it’s only the Component or Template definitions that should avoid relying on them. It lengthens your site downtime during deployments because you need time to get them all back in place, and it makes it hard for you to track what is and isn’t missing.
Drupal acquia manual#
If you use a lot of Blocks to define components or templates in Acquia Site Studio, this makes for painful deployments since it creates a lot of manual work. This requires you to go back through on these sites, create those blocks, place them in the Acquia Site Studio hidden region of the theme, configure them, and put them back into those components. What happens is that you can deploy your changes to staging or production only to find that blocks you used won’t be present. If you can, try to avoid placing and using Block entities within Acquia Site Studio Component or Template definitions.īlocks are content entities in Drupal and won’t be exported (just like Media entities mentioned above). Avoid Using Blocks within Components or Templates Otherwise, even though deployments will appear to be successful those images won’t be present, and this can be hard to track down. You may even get several errors when trying to import packages on higher environments if this is not set properly.īy setting the image browser for config correctly, it ensures that the image data is included within the exported files Acquia Site Studio produces. Even if you add these to staging or production, future deployments will reset those values.
If you select browsers that use Media entities for this, all your exports will contain ID references to media entities that won’t exist on other environments, and your deployments will be missing these files. If this is not set, you can’t successfully export component or template definitions that contain images, icons, or other static assets. Make sure that the image browser for config is either set to no image browser or a file-based browser like IMCE. When setting up Acquia Site Studio, you have an option of setting the image browser to use within Components: This setting is one of the most important to get right for smooth deployments with Acquia Site Studio. Ensure the Image Browser for Configuration is Correct The package export should only contain items relevant to Acquia Site Studio. Making changes to them will be easier to export and deploy as normal Drupal configuration rather than using Acquia Site Studio to generate a new package and deploy. This way, Image styles and Views are independent from Acquia Site Studio. Image styles and Views should be tracked by the normal Drupal configuration system. For most Drupal projects you’ll make extensive use of Image styles and Views to construct parts of your website, whether it’s used within Acquia Site Studio components or not. It’s wise to uncheck Packages, Image styles, and Views. You want all of these, except for three of them. For the “Full” package (i.e., everything) you can select what to include in the export. In the administrative area of Site Studio or using Drush on the command line you can export all the configuration related to Acquia Site Studio into a package. Do Not Export “Everything” into a Single Package
Drupal acquia full#
Instead, export the Acquia Site Studio settings as a full package or into individual package(s) you can deploy to staging or production environments. Having Acquia Site Studio configuration files mixed into the normal Drupal configuration can present import errors on deployments that are difficult to resolve. The reason these files are ignored is because they’re exported and tracked in the package(s) Acquia Site Studio creates. The objective is to ensure Drupal is unaware of Acquia Site Studio.
Drupal acquia license key#
You can also add it if you want, but you must re-enter the license key on each site (dev, staging, and production). The only file tracked by normal Drupal configuration is ttings which holds basic information and your Acquia Site Studio license key.
In the Config Ignore settings in the Drupal admin, set these patterns: Acquia Site Studio has its own packaging system to track configuration that we highly recommend using. This is useful when you don’t want to have configuration overridden or imported. This means that it won’t export or import configuration that matches anything you set. The Config Ignore module lets you list names of configuration sets to ignore. Before installing Acquia Site Studio, make sure you have downloaded and enabled the Config Ignore module first.
0 kommentar(er)
