Articles in this section

See more

Pearl Theme on Magento Cloud - how to overcome read only file system limitation

Avatar
Support Tier 2
  • Updated
Follow
 
Main reasons and how to overcome the read only limitation:
 
 
Case 1: Static Content Symlinks Enabled 
 
The file "/app/pub/static/frontend/Pearl/weltpixel_custom/en_US/css/styles-l-temp.css" cannot be deleted Warning!unlink(/app/pub/static/frontend/Pearl/weltpixel_custom/en_US/css/styles-l-temp.css): Read-only file system : default
 
In some cloud environments pub/static can be symlinked during the deployment to a folder outside the Magento application folder, that is why this folder is read-only and theme LESS/CSS files cannot be regenerated under /pub/static/frontend/Pearl/weltpixel_custom/en_US/css/.

You can make 'pub/static' folder writable by disabling the static content symlink. Create STATIC_CONTENT_SYMLINK variable as you can see in below picture.
 
STATIC_CONTENT_SYMLINK : disabled
 
 
symlink.png
 
 
 
The folder pub/static will now be writable, but deployment time will be increased due to copying static during the deployment. When you go live, you can enable symlinks on the Production environment for faster deployments but for staging and development we suggest removing symlinks in order to be able to regenerate theme LESS/CSS files.
 
 
 
 
 
 
Case 2: Deployment hooks 
Try setting the deployment hooks in the deploy phase instead of the build phase.
 
# The hooks executed at various points in the lifecycle of the application.
hooks:
# We run build hooks before your application has been packaged.
build: |
php ./vendor/bin/m2-ece-build
# We run deploy hook after your application has been deployed and started.
deploy: |
php ./vendor/bin/m2-ece-deploy
php ./bin/magento weltpixel:less:generate
php ./bin/magento weltpixel:css:generate --store=default
 

Related articles

Comments

0 comments

Please sign in to leave a comment.