Bedrock Capistrano Deployment Theme Path Update

Hello everyone! I set up Bedrock and Capistrano today to streamline my Wordpress development workflow. Everything is working except the minor issue that whenever I deploy using Capistrano, there is the famed white screen of death on the front-end for Wordpress.

I checked this pull request: and installed wp-cli on my bluehost vps account and uncommented the update_options_task task in deploy.rb, but this did not resolve the issue.

Here’s the relevant output from my deploy command:

G[3245eedf] Finished in 0.648 seconds with exit status 0 (successful). DEBUG[c0a0ab36] Running /usr/bin/php-cli /home/xxxx/bin/wp-cli.phar core is-installed on DEBUG[c0a0ab36] Command: cd /home/xxxx/public_html/staging/releases/20160708214213 && ( WP_ENV=staging /usr/bin/php-cli /home/xxxx/bin/wp-cli.phar core is-installed ) DEBUG[c0a0ab36] Finished in 1.119 seconds with exit status 0 (successful). DEBUG[57221cff] Running /usr/bin/php-cli /home/xxxx/bin/wp-cli.phar option get stylesheet_root on DEBUG[57221cff] Command: cd /home/xxxx/public_html/staging/releases/20160708214213 && ( WP_ENV=staging /usr/bin/php-cli /home/xxxx/bin/wp-cli.phar option get stylesheet_root ) DEBUG[57221cff] Finished in 1.115 seconds with exit status 1 (failed). DEBUG[9dfafc60] Running /usr/bin/php-cli /home/xxxx/bin/wp-cli.phar option get template_root on DEBUG[9dfafc60] Command: cd /home/xxxx/public_html/staging/releases/20160708214213 && ( WP_ENV=staging /usr/bin/php-cli /home/xxxx/bin/wp-cli.phar option get template_root ) DEBUG[9dfafc60] Finished in 1.069 seconds with exit status 1 (failed). DEBUG[eab84f39] Running /usr/bin/env ls -x /home/xxxx/public_html/staging/releases on DEBUG[eab84f39] Command: ( WP_ENV=staging /usr/bin/env ls -x /home/xxxx/public_html/staging/releases ) DEBUG[eab84f39] 20160708213843 20160708214213 DEBUG[eab84f39] Finished in 0.644 seconds with exit status 0 (successful).
Has anyone else run into issue?

Thanks a bunch, guys.

You’ll need to turn on verbose mode for Capistrano to see what’s really going on. Or just try running those commands yourself manually. Can’t really do much without the actual error output.