Deploying on STRATUS
MageMojo has created STRATUS to be as simple as possible for code deployments. Despite the incredible sophistication of the STRATUS cloud platform, STRATUS deployments are fairly straightforward and familiar. If you have Zero Downtime deployment enabled or wish to enable it, please follow the ZDD guide.
Before deploying code to a STRATUS instance:
- Make sure that all symlinks are using absolute paths.
- Note that CloudFront may take up to 15 minutes to clear.
After deploying, you should run the following additional commands:
/usr/share/stratus/cli autoscaling.reinit; sleep 150s; /usr/share/stratus/cli cache.all.clear;
autoscaling.reinitperforms a rolling update of the php-fpm containers. When a store is scalled this will ensure a seamless update across the scaled php-fpm services.
sleep 150spauses to wait rolling update of php-fpm containers to complete because
autoscaling.reinitis called asynchronously.
If files (other than js, css files that may still be clearing in CloudFront) are not clearing properly from CloudFront or if the Magento cache status (on/off) is reported differently between the CLI and the Magento Admin, use the following following the deployment:
/usr/share/stratus/cli crons.stop; php bin/magento maintenance:enable; n98-magerun2 cache:disable; php bin/magento cache:flush; /usr/share/stratus/cli cache.all.clear; php bin/magento setup:upgrade; php bin/magento setup:di:compile; php bin/magento setup:static-content:deploy -f -j 10; php bin/magento indexer:reindex; n98-magerun2 cache:enable; /usr/share/stratus/cli autoscaling.reinit; sleep 150s; php bin/magento cache:flush; /usr/share/stratus/cli cache.all.clear; php bin/magento maintenance:disable; /usr/share/stratus/cli crons.start;
You can see pod status change during deployment under the General-> Pods section.