I have been building a new site with Trellis. A couple months ago I set up a staging server which I have been frequently deploying to using the
deploy.sh script provided by Trellis. Things have gone smoothly up until now.
I have added plugins to my project without issue in the past but yesterday I added a new plugin (specifically Single Category Permalinks) to my
composer update && composer install locally (thus modifying my
composer.lock file) and redeployed my local instance. The plugin showed up as expected and I was able to use it in Wordpress.
I committed my changes and attempted to deploy to staging with the usual command:
./deploy.sh staging mywebsite.com.
The deploy failed at the
Wordpress Installed? task. I went to my staging server and got back a blank page. I also ssh’d into my server and verified that Wordpress was installed.
Nervous, I checked out the most recent commit that been deployed and deployed that to staging. This went fine and the staging site was running again.
I’m at a loss for why this is happening. The only change between the two commits is the addition of this new plugin. In the past I have added plugins to the site with no issue. Why would the presence of this plugin cause the deploy script to not detect the Wordpress installation?
Any ideas? I searched around this forum and couldn’t find any similar issues. I am new to Trellis and not sure how to debug this. Would appreciate any debugging tips or solutions. Apologies if there are relevant details missing from this post, let me know what they are and I will add them.