Deploy Faster, Deploy Smarter
Magento 2 has a powerful tool-kit for enterprise-level deployments. All this is harnessed into a CLI which some might find daunting at first, however with MDOQ managed Magento hosting and some helpful tips, this need no longer be the case.
bin/magento deploy:mode:set production
This is the easiest way to put your site into production mode. Among other things this will create a folder/file structure of deployed front-end assets for each theme and language you have active.
Even though with MDOQ your deployment timing does not affect any downtime on production, its always prudent to understand and reduce this in order to tighten up your development cycle.
| Theme/Locale | en_US | en_GB |
|---|---|---|
| Admin | X | X |
| Blank | X | X |
| Luma | X | X |
| YourTheme | X | X |
As the table above illustrates, typically the static assets are typically generated 8 times for different scenarios.
If you operate a single-store single language then you could try checking if ALL your Admin users are using the same locale. If ANY users are using different locales, then this will have a multiplying effect on every theme.