But that command comes on a brand new Bedrock install. It seems that lines are used to copy the .env.example file to the site root as .env file when it’s first installed… You mean that I should remove those lines? I don’t know how is that related to the fact that functionality from an independent composer plugin isn’t fired.
I don’t know if it’s a problem with Trellis or the Koodimonni composer plugin itself, but as If I access the production server via SSH, do a manual composer install and everything works fine, it seems like something in the deploy process is not firing the same way as I do it mannually.
Let me sum up and see if I’m wrong with the deploy process:
- Every time I do a deploy to production a new composer install is fired in the new site release folder ( https://gist.github.com/cfaria/46284212707f7fa1dcebd7edcfe01e21#file-build-after-yml-L20-L22 ). Then, that composer install should install all the plugins I have in my composer.json and everyone should do all the operations needed.
- So, in the composer-dropin-installer plugin from Koodimonni, loaded in my composer.json file ( https://gist.github.com/cfaria/46284212707f7fa1dcebd7edcfe01e21#file-composer-json-L42 ), as the composer plugins are being installed (beacause it’s a brand new composer install), the onPackageInstall function on that plugin ( https://gist.github.com/cfaria/46284212707f7fa1dcebd7edcfe01e21#file-dropin-php-L83-L93 ) should be fired. That function is in charge of copying the files and that is what is not happening when I use the Trellis deploy role.
Maybe I should debug the composer-dropin-installer and see if everything works when deploying. Maybe the files aren’t there when the plugin is trying to move them…
Let me debug that and I’ll come with the results.