compare · a project structure
Loopress vs Bedrock.
Bedrock restructures a WordPress project around Composer. Loopress leaves the site as it is and puts its configuration and code in Git.
| Roots Bedrock | Loopress | |
|---|---|---|
| Project layout | Its own: core in web/wp, code in web/app, settings in .env | The stock wp-content layout your host already runs |
| Plugins | Composer, in your repo | A lockfile in loopress.json, or your composer.json |
| Deploy | Usually Trellis, which needs SSH and control of the server | lps push over the REST API, no SSH |
| Configuration in the database (menus, options) | Not covered | Pulled as files, pushed back, diffed |
| Existing sites | A migration to the new layout | Connect and pull, nothing to move |
Same task, both ways
Ship a menu change from staging to production.
Roots Bedrock
- Nothing in the repo describes the menu
- Redo the change by hand in production's wp-admin
Loopress
$ lps menu pull --env staging $ git commit -am "feat: footer menu" $ lps menu push --env production
Pick Roots Bedrock when
You start a site from scratch, own the server, and want Composer to manage everything including WordPress core.
Pick Loopress when
You look after sites that already exist, on hosts you don't control, and the risky changes are the ones made in wp-admin.
All comparisons · ACF Local JSON · WP Staging and Duplicator · WP Migrate · VersionPress