Bedrock v2

[retlehs]

Bedrock will be getting a major version update 💥 We'll be making changes to the directory structure and configuration system to better align with modern PHP practices.

These directory changes mean we'll need to update Trellis to accommodate the new structure. It will also mean we'll need to update any other tools that interact with Bedrock sites, such as Valet/Herd drivers, deployment scripts, docs/tutorials, etc.

Directory structure

• Rename web/ directory to public/ to better align with modern PHP practices
• Make the app/ directory (wp-content) the public web root 🔨

Configuration

• Adopt wp-config v2
  • New fluent configuration API
  • Simplified environment handling
• Drop WP_ENV in favor of WordPress core's WP_ENVIRONMENT_TYPE
  • Ref Improve support for environment types and fix description of plugin bedrock-disallow-indexing#1

---

Bedrock v1:

├── composer.json
├── config/
│   ├── application.php     # Primary wp-config
│   └── environments
│       ├── development.php
│       ├── staging.php
│       └── production.php
├── vendor/                 # Composer dependencies
└── web/                    # Public document root
    ├── app/                # WordPress content dir
    │   ├── mu-plugins/
    │   ├── plugins/
    │   ├── themes/
    │   └── uploads/
    ├── index.php
    ├── wp-config.php
    └── wp/                 # WordPress core

Bedrock v2:

├── config.php              # Primary wp-config
├── composer.json
├── vendor/                 # Composer dependencies
└── public/                 # Public document root (renamed from web/)
    ├── index.php
    ├── wp-config.php       # Required wp-config.php from WordPress, loads our wp-config.php from the project root
    ├── mu-plugins/
    ├── plugins/
    ├── themes/
    ├── uploads/
    └── wp/                 # WordPress core

[dalepgrant]

How set are you on the names? Having two files as wp-config.php will get confusing, you're already referring to them as 'primary' and 'required' to differentiate. The one required by WP is obviously going to have to stay as wp-config.php; could the other change to just config.php, or app-config.php? 🤷‍♂

 ├── composer.json
 ├── vendor/                 # Composer dependencies
-├── wp-config.php           # Primary wp-config
+├── config.php              # Consolidated config
 └── public/                 # Public document root (renamed from web/)
     ├── index.php
     ├── wp-config.php       # Required wp-config.php from WordPress, loads our config.php from the project root
     ├── mu-plugins/
     ├── plugins/
     ├── themes/
     ├── uploads/
     └── wp/                 # WordPress core

Edit: make diff clearer

[retlehs]

@dalepgrant Great idea, thank you! 🙏 Just updated the OP

[cphillipsusu]

These look like great changes! We are just getting started with a new Bedrock site - do you anticipate any easy upgrade path to v2 or if we are just getting started does it make sense for this new version to be released?

[lagiosdi]

I recommend organizing the config.php file within a dedicated folder named config to enhance compatibility, particularly with Acorn, in addition to the Bedrock setup. This structure will offer greater flexibility and maintain alignment with Acorn's requirements.

[retlehs]

That’s not possible — even if Acorn was a Bedrock requirement, Acorn is booted after WordPress is already loaded

[lagiosdi]

I understand the procedure and the order in which things are loaded.

However, for administrative purposes, it's more efficient to have all configuration files in the same folder. In larger projects, where multiple configurations are used, it's much easier to manage everything from one central location. This approach helps streamline the process and maintain consistency across the project.

[retlehs]

It’s not possible.

[stevedsross]

Very cool update.

I was messing around with my own composer setup while retaining the original wordpress directory structure and learned that wp-config.php can exist one level up from the docroot in the filesystem and doesn't actually need to be in the docroot directory at all.

I had it working here: https://github.com/badegguk/Wordpress-Composer-Classic-Structure

Would that work for the new Bedrock too?

[jasperf]

The updated structure in Bedrock v2 looks great. Switching from web/ to public/ for the document root brings it in line with modern PHP practices—especially Laravel, which also uses public/. This change improves consistency for projects that combine Bedrock (and Sage) with Laravel (web root mention), such as in monorepos or VPS/container-based environments where you have full control over the web root configuration.

[robrecord]

Forgive me for not adding anything useful to the conversation, but:

Every time Roots seeks to advance their projects like this, I feel excited and proud that I'm a Roots user. Well done team 👏

[UnknownChick]

Hello,

Any news about this update ?

[retlehs]

roots/wp-config#20 has had some recent work done, including adding a hooks system to wp-config so that packages can modify/add configuration settings

I also have WIP for a new bedrock-multisite package that revives https://github.com/roots/multisite-url-fixer and adds automated multisite configuration support with the new wp-config hooks system

There's WIP for Bedrock v2 support in Trellis as well: roots/trellis#1586

I'll eventually be pushing to this repo with the changes described in the OP and tagging an alpha or beta release, but there is no ETA. If you're antsy, https://roots.io/radicle/ is already available and has a lot of the changes coming in Bedrock v2.

[retlehs]

Getting closer. Wrapped up the fluent API changes on https://github.com/roots/wp-config which is about to get a v2 beta tag.

See https://github.com/roots/wp-config#full-example for how this is going to look in Bedrock, with a single config.php file in the root instead of the config/ directory

Radicle users can see these config changes in action in this draft PR: https://github.com/roots/radicle/pull/313