Skip to content

WordPress

Choosing WordPress when you create a site runs the whole install: core downloaded, the database created, wp-config.php written, an admin user made. When it finishes you have a working site on real HTTPS.

WP-CLI 2.12.0 and Composer 2.10.2 are bundled, so nothing needs installing separately.

One click opens wp-admin as an administrator. No password, no password manager, no admin/admin on twelve local sites.

Terminal window
rex site login myshop.rex
rex site login myshop.rex --print # print the link instead of opening it

Everything below is in the app, and mirrored on the CLI as vetted WP-CLI operations:

Users, roles and passwords too:

Terminal window
rex wp myshop.rex user list
rex wp myshop.rex user create editor editor@example.com --role=editor
rex wp myshop.rex user set-password admin
Terminal window
rex wp myshop.rex search-replace old.rex new.rex --dry-run
rex wp myshop.rex cache-flush
rex wp myshop.rex cron run
rex wp myshop.rex maintenance on
rex wp myshop.rex core versions
rex wp myshop.rex core switch 6.7.1

search-replace defaults to showing you what it would do. Run it with --dry-run first — it is the operation most likely to be right in intent and wrong in scope.

The manager is a vetted set of operations rather than an arbitrary WP-CLI passthrough. For anything outside it, the site’s Terminal tab gives you a real shell, already in the docroot, with the site’s own PHP and wp on PATH:

Terminal window
wp plugin list --status=active --format=json
wp db query "SELECT option_name FROM wp_options WHERE autoload='yes'"

Every message the site sends is caught by Mailpit and none are delivered. That includes the password reset you are about to trigger, which is usually how people discover it.

wp dist-archive builds a distributable plugin or theme zip from a repository asset, into ~/Downloads. Useful when the thing you are developing locally has to ship as a zip.