kellerkinderde / deployer-shopware5 Goto Github PK

On kellerkinder:vendors task breaks with:

Warning: Ambiguous class resolution, "Doctrine\ORM\Persisters\Entity\BasicEntityPersister" was found in both "$baseDir . '/engine/Library/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php" and "/www/casamia.local/releases/2/sr
c/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php", the first will be used.
Warning: Ambiguous class resolution, "Doctrine\Common\Proxy\AbstractProxyFactory" was found in both "$baseDir . '/engine/Library/Doctrine/Common/Proxy/AbstractProxyFactory.php" and "/www/casamia.local/releases/2/src/vendor/doctrine/
common/lib/Doctrine/Common/Proxy/AbstractProxyFactory.php", the first will be used.
Skipped installation of bin bin/doctrine-dbal for package doctrine/dbal: file not found in package
Skipped installation of bin bin/doctrine for package doctrine/orm: file not found in package
Skipped installation of bin bin/doctrine.php for package doctrine/orm: file not found in package
./build/composer-post-update-cmd.sh
sh: 1: ./build/composer-post-update-cmd.sh: not found
Script ./build/composer-post-update-cmd.sh handling the post-update-cmd event returned with error code 127

What about using a composer based install?
I am thinking of

• cloning shopware/composer-project
• adapt content of .env and composer.json (for different shopware versions)
• run composer install/update

By using composer we could handle dependencies effectively.
What is your take on this?

cheers tom

Hi,

Thanks a lot for sharing this code.
At the moment i am going through the tasks of deploy:staging trying to figure them out and getting them to run.
Now when i do deploy:update_code my code gets cloned to {{release_path}}.

• /var/www/mobl/releases/2/custom/plugins/
• /var/www/mobl/releases/2/themes/Frontend/Mobl
  etc.

When i do kellerkinder:shopware:configure, kellerkinder:shopware:plugins expects the plugin code to be in {{shopware_public_path}}

• /var/www/mobl/releases/2/web/custom/plugins/

defined by: set('shopware_public_dir', 'web');
Am i doing something wrong here?
When copying the plugins from release_path to shopware_public_path it works.
So this could be done by overwriting deploy:update_code to use shopware_public_path instead of release_path.
On the other hand i do not really understand why there is a shopware_public_dir at all.
So i am probably missing something entirely.

TIA
tom