WordPress Bedrock on Enhance

Luuk

Does anyone have experience with WP Bedrock (https://roots.io/bedrock/) on Enhance and how to make it show up on the applications? So we can login via Enhance?

Adam

composer is installed by default on Enhance so you can use it via the customer ssh environment.

If the deployed application has a relatively standard wp-config then Enhance should detect it when you click "discover new installations" on the apps page.

Luuk

Adam
Hey Adam,

I guess to the nature of bedrock it is not possible to get it discovered in enhance.

The organization of Bedrock is similar to putting WordPress in its own subdirectory but with some improvements:

In order not to expose sensitive files in the web root, Bedrock moves what's required into a web/ directory including the wp/ source, and the wp-content source.
wp-content has been named app to better reflect its contents. It contains application code and not just "static content". It also matches up with other frameworks such as Symfony and Rails.
wp-config.php remains in the web/ because it's required by WP, but it only acts as a loader. The actual configuration files have been moved to config/ for better separation.
vendor/ is where the Composer managed dependencies are installed to.
wp/ is where WordPress core lives. It's also managed by Composer but can't be put under vendor due to WP limitations.

asmdot

I'm hosting Bedrock sites on Enhance, and while they work absolutely fine, the "Discover existing" function does not find a valid Wordpress install, and this is with a stock Bedrock. My guess is that even if it did manage to find it, a whole bunch of the integration functionality wouldn't work, as the path structure is pretty different.

While it'd be lovely to take advantage of the shortcut for accessing the admin section, I'd disable almost all of the integration features (plugin / user / theme management) anyway, so I'm not sure it's a great loss? I really haven't played with the integration piece enough to know what I might be missing. I use MainWP for managing sites already, which has worked fine for several years.

I'm also not sure how they'd support the idea of installing a Bedrock site - you absolutely shouldn't be using Bedrock like that, it should live in a Git repository and a build of it should be deployed to your server.

asmdot

My personal gripe isn't so much with the integration stuff, it's with the cloning tool - it has no idea about .env files, and while it manages to figure some stuff out, the site it copies across simply does not work. I could fix the things that are left incorrect, but honestly, it's faster to just do the whole clone process manually. It's a bit annoying because it means I have to explain to customers that there's this lovely looking feature there for them, but they can't use it because it doesn't work, but that's the price to pay for having a devops workflow I guess.

twest

asmdot I disabled it in settings, and disabled staging. Can't beat the reliability of doing it manually at the moment.