I agree with @swalkinshaw’s post above. I had all this typed so I’ll share it anyway…
Normally your steps should work.
Could you try temporarily replacing your staging repo
value with the following (and leave the repo_subtree_path
commented out):
repo: git@github.com:roots/bedrock.git
If deploying this basic bedrock repo succeeds, it suggests that your own repo doesn’t have the composer.json file in the root (perhaps you simply haven’t yet pushed your local git changes to your remote repo?).
If the above test still fails with the same message, could you try temporarily editing the production group_vars/production/wordpress_sites.yml
, replacing the repo
value again with the basic bedrock repo above and commenting out the repo_subtree_path
, then run your deploy again, still with -e env=staging
? If now the deploy succeeds, it suggests that production variables are coming in to play even when you use -e env=staging
, which would likely be a symptom of this problem (see link for solution).