Since we have multiple language packs, we had to commit a clean composer.{json,lock} to each machine.
We did this for WordPress core, for the core language packs and for plugins that had language packs. Meaning, for each path that was shared among packages, we had to commit the clean up, and then commit the packages back again. This seemed to work fine for staging, so we repeated the steps for production.
its working now flawlessly. thanks everyone for their contributions.
Hi guys, it started to do the same thing for me on my staging environment.
It has the same problem even with a newly provisioned instance.
Is it just the composer install or does it have anything to do with wordpress-install task that is not present in the server.yml (I know that probably won’t be the case, but I’m trying to think of different ipothesis).
I attempted to clear the composer cache, reinstalled manually or with the task itself but no success.
Somewhere in the deploy WordPress doesn’t get installed as it should…
I noticed most of the deploy hooks have changed some in the latest version of Trellis. I will compare them to my current deploy-hooks to see if anything has changed.
Did you miss the solution in this thread? What you did isn’t going to prevent the issue from happening again on your next deploy, follow the steps here:
I am just trying to setup a new project using bedrock command:
composer create-project roots/bedrock project1
and I am getting this error :
Installing johnpbloch/wordpress (4.7.3): Cloning eef7c0520b from cache
eef7c0520b1e7187cd2cd7540dc997c4c3b0340a is gone (history was rewritten?)
then it crashes. I have tried clearing my composer cache. It still doesnt work. I am not sure if i can try a composer.json update as this is a new project and I dont have a composer.json. Help!!
I’ve run into problems with composer on stage and production.
I’ve tried clearing the cache multiple times to no avail.
I recently re-organised my package repo and added an ssl certificate. This works fine for dev.
When I try to run a deploy, it seems to be trying to load packages via the old http urls that are no longer in my updated composer.json. I’ve checked that the correct composer.json is in my remote git repo.
I can’t understand where this old composer.json is coming from or how I can get rid of it.
I’m running a version of trellis from late March and ansible 2.2.2.0.