This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » eZ Publish 5 Platform » Git deployment with composer install

Git deployment with composer install

Git deployment with composer install

Thursday 16 October 2014 4:15:58 pm - 1 reply

On a eZPublish 5.3.x site with alot of legacy fallback logic, how safe/unsafe is it to run composer install per deployment?

 export SYMFONY_ENV=prod && composer install --prefer-dist --no-interaction --no-dev --optimize-autoloader

I've noticed some big changes in composer.json lately, thus wondering if the composer.json distributed to enterprise customers are defined good enough to run "blindly" in git hooks.

Feedback and thoughts/best-practices are very welcome!

- Harald

Modified on Thursday 16 October 2014 4:38:24 pm by Harald Tollefsen

Tuesday 21 October 2014 12:21:34 am

It is a pity that this topic is not widely discussed. Most probably it is so because Composer in eZP5 is still something new and didn't get acclimatized enough blunk.gif Emoticon

To subject: several days ago I prepared composer.json to install eZP 5.3 for several enviromments including prod. This solution is still in a test phas, but seemes to be working. But I reworked bundled composer.json to adapt to project requirements.

It is easy easy to install legacy but another step (for me) is to install legacy bundles using composer.


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from