Skip to content

Create a site

New site in the app, or:

Terminal window
rex site create myshop.rex --type wordpress
Option Values Default
Type wordpress, php, laravel wordpress
PHP any installed minor, 7.4–8.5 your configured default
Web server nginx, frankenphp, apache nginx (shared)
Database mysql, mariadb mysql
Multisite subdomain, subdirectory off
Blueprint any saved blueprint none

The CLI mirrors the dialog exactly, because it is the same code:

Terminal window
rex site create shop.rex \
--type wordpress \
--php 8.3 \
--server apache \
--db mariadb \
--multisite subdomain

Choosing WordPress runs the install for you — core downloaded, database created, wp-config.php written, admin user made. When it finishes the site is a working WordPress at https://<domain>, and magic login opens wp-admin without a password.

Multisite is chosen at create time because WordPress bakes the choice into the database. Subdomain multisite gets a wildcard certificate so sub.myshop.rex works too.

--type laravel and --type php skip the WordPress install and give you a docroot with the right server config. For Laravel that means the docroot points at public/.

Neither creates a database unless you ask for one — a Laravel project usually brings its own .env expectations, and guessing at them would be worse than leaving it to you.

New sites are provisioned into rexenv’s Sites folder inside ~/Library/Application Support/dev.rexenv.rexenv/, unless you moved that folder in Settings.

To serve a project where it already is, use Link an existing folder instead — that path never copies your files.

The first site you create downloads the components it needs: a PHP version, nginx, the database engine, Caddy. Later sites reuse them and are quick. See Requirements for the total.