fballiano / homebrew-mageutils

Magento utilities Tap for Homebrew

If you find my work valuable, please consider sponsoring

My Magento1/OpenMage modules:

• Orphan images cleaner
• Autodelete product images
• CloudFlare Turnstile
• CSS/JS versioning based on last git commit hash (or timestamp failback)
• Defer Javascripts
• devenv.sh environment for OpenMage development
• Empty categories hider
• Cache regeneration lock
• Full catalog translate via Google Translate or others
• Recently viewed products support for Varnish/Turpentine
• Default category sort order direction

My Magento2 projects:

• devenv.sh environment for Magento2 development
• Defer Javascripts
• Default category sort order direction
• Docker Magento2: Cluster ready Magento2 + Varnish 7 + PHP 8.1 + Redis 6.2 + Elasticsearch 7.17 + SSL infrastructure

Others:

• Magento utilities for HomeBrew
• Bridge class to replicate Zend_Db in Zend Framework 2

homebrew-mageutils's Issues

Pestle 1.5.1 and 1.5.2 Release

👋 Hey there -- we just released pestle 1.5.1 and a quick 1.5.2 right after that.

$ openssl sha256 pestle-1-5-1.phar 
SHA256(pestle-1-5-1.phar)= 438cfe74bfd860d52570e0dd1a1a2b09d57ced19bd2ea63020a1db132361e553

$ openssl sha256 pestle-1-5-2.phar 
SHA256(pestle-1-5-2.phar)= 4796f9def1f0c08c646f6b9625f417134dcdc2a2ec34514bdc718d71b35c475b

and we're also going to try publishing them with versioned numbers

curl -LO http://pestle.pulsestorm.net/pestle.phar
curl -LO http://pestle.pulsestorm.net/pestle-1-5-2.phar
curl -LO http://pestle.pulsestorm.net/pestle-1-5-1.phar

Not sure how any of the above will impact you, but did want to let you know.

Pestle Not Working?

I'm on MacOS 10.14.6 and this happens when I try to run the brew installed pestle

$ pestle
PHP Fatal error:  Uncaught UnexpectedValueException:    RecursiveDirectoryIterator::__construct(/Users/astorm/pestle _modules/modules/): failed to open dir: No such file or directory in phar:///usr/local/Cellar/pestle/1.5.0/bin/pestle/modules/pulsestorm/cli/build_command_list/module.php:21

Before I dig into this, is this is known issue? What would you need to reproduce/debug/fix this?