Static content deployment best practices

Make sure to follow deployment guidelines:

• For Adobe Commerce on-premises (all versions), see Deployment Overview in our developer documentation.
• For Adobe Commerce on cloud infrastructure (all versions), see Cloud deployment process and Static content deployment strategies in our developer documentation.

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 (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:

• Adobe Commerce on-premises (all versions): Technical Details in our developer documentation.
• Adobe Commerce on cloud infrastructure (all versions): Deployment process - Phase 2: build in our developer documentation.

Check your SCD strategy. The quick strategy is the default. For more information:

• Adobe Commerce on-premises (all versions): Static files deployment strategies in our developer documentation.
• Adobe Commerce on cloud infrastructure (all versions): Deploy variables - SCD_STRATEGY in our developer documentation.