Adobe Commerce stores themes in the file system, which is accessible during the build phase however, Adobe Commerce stores locales in the database. Generating static content requires access to themes and locales. Instead of copying files to a mounted drive, it creates a symlink from the. Generating static content during the build phase with minified HTML is the optimal configuration for zero-downtime deployments, also known as the ideal state. Therefore, generating static content during the build phase is the most optimal. However, if the content file does not exist in the cache it generates at the moment it is requested, which adds load time to the user experience. Generating static content on demand seems like the optimal choice. Even with minified HTML, each content file must be copied to the mounted ~/pub/static directory, which can take a long time. As seen in the following chart, generating static content during the deploy phase is the least optimal choice. Choosing a deploy strategyĭeployment strategies differ based on whether you choose to generate static content during the build phase, the deploy phase, or on-demand. You can configure these theme settings with the SCD_MATRIX environment variable. For example, you can deploy the magento/backend theme in English and a custom theme in other languages. You can save more deployment time and disk space by reducing the number of unnecessary theme files. file.īeginning with the ece-tools package version 2002.0.13, the default value for the SKIP_HTML_MINIFICATION variable is set to true. You can activate this by setting the SKIP_HTML_MINIFICATION global environment variable to true in the. You can improve the SCD load time during the deployment process if you skip copying the static view files in the var/view_preprocessed directory and generate minified HTML when requested. You can use bundling and minification to build optimized JavaScript and HTML content during static content deployment. You have several options or strategies to help you improve the deployment time depending on your needs. For example, the default strategy generates static content during the deploy phase when the site is in maintenance mode however, this deployment strategy takes time to write the content directly to the mounted pub/static directory.
To learn to enable CSS file optimization, refer to Frontend Developer Guide > Cascading style sheets (CSS) > CSS merging, minification and performance in our developer documentation.Static content deployment (SCD) has a significant impact on the store deployment process that depends on how much content to generate-such as images, scripts, CSS, videos, themes, locales, and web pages-and when to generate the content.To learn more about optimizing resource files, refer to Optimizing Resource Files in our user guide.You can also enable Adobe Commerce built-in bundling (basic bundling) from the command line: php -f bin/magento config:set dev/js/enable_js_bundling 1.You can turn on merging or bundling in the Commerce Admin UI (merging and bundling cannot be enabled at the same time): Stores > Settings > Configuration > Advanced > Developer > JavaScript Settings.Run this command locally: bin/magento config:set -lock-config dev/js/minify_files 1.To enable JS minification in Adobe Commerce on cloud infrastructure: On the Admin sidebar, go to Stores > Settings > Configuration > Advanced > Developer > JavaScript Settings.
0 kommentar(er)
