PascalBrouwers

You could also try: ``` SSHKit.config.command_map[:php] = "/usr/bin/php74" SSHKit.config.command_map[:composer] = "/usr/bin/php74 /usr/local/bin/composer" SSHKit.config.command_map[:magento] = "/usr/bin/php74 -f bin/magento --" ``` (If `/usr/bin/php74` is the location of your php 7.4.x)

Or keep the sitemap in /pub/sitemaps/ and create a symlink in /pub to itself: ``` cd pub ln -sfn pub . ``` this way you can serve from /pub and...

Nothing is stopping you from adding it to your own `deploy.rb`, though it would be nice to have it as default in the shared dir.

That's not possible, but I should make sure that running commands between release_path and current_path the cache should be flushed.

Small update: you also need to fix the autoloader because that is cached too. So run this too: `invoke!('magento:composer:install') if fetch(:magento_deploy_composer)`

Trying to get a fail-safe method for this but it feels like there isn't one. As soon as you flush the redis cache there is the possibility that a visitor...

Also an issue when running php 7.2 / 7.3 in your current release and the latest release need php 7.4 Running composer install in both directories isn't going to work...

Decided to go with using a different cache prefix for each deployment. This way generated files and other caches don't interfere with each other during a deploy for a site...

Added some fixes when categories without childs would not be processed. @Iazel would be nice if this could be merged.

Sure