Static content deploy best practices in Adobe Commerce
This article talks about static content deploy (SCD) best practices in Adobe Commerce to help avoid issues where the static content would not be available on your website.
Affected products and versions
- Adobe Commerce on-premises, all versions
- Magento Open Source, all versions
- Adobe Commerce on cloud infrastructure, all versions
To avoid an issue with static content not being available on your website, follow these best practices to make sure your static content is both configured and deployed correctly:
- Make sure to follow deployment guidelines:
- For Adobe Commerce on cloud infrastructure (all versions), ensure that ece-tools is on the newest release. See: Update ece-tools version in our developer documentation.
- For Adobe Commerce on cloud infrastructure (all versions), make sure that static content is deployed during the build phase rather than the deployment phase. See: Configuration management for store settings - Static content deployment performance in our developer documentation.
- Make sure that you do not have long-running cron jobs and kill any long-running cron processes. Long-running cron jobs can take up CPU resources and potentially greatly increase deployment time.
- For Adobe Commerce on-premises and Magento Open Source (all versions), check that the
php process in CLI has access to the
pub/static directory. Otherwise, you could face an issue where a static content deploy will be unable to write files to that directory. For more information: File systems access permissions in our developer documentation.
- Ensure the
generated directory is not a shared directory across builds; otherwise, builds could fail randomly. For more information:
- Check your SCD strategy. The quick strategy is the default. For more information:
In our developer documentation:
In our support knowledge base: