Sites

A site in rexenv is a domain, a docroot, a PHP version, a web server, a certificate and (usually) a database. Creating one wires all of that together; the rest of this section is about the parts you can change afterwards, which is all of them.

Three ways to start

Create a new siteWordPress, Laravel or blank PHP, provisioned into rexenv's Sites folder.

Link a folder you already haveServe a project where it already lives. Nothing is copied or moved.

Clone from a git repositoryClone, install dependencies, build assets, and serve the result.

What every site gets

• A domain — <name>.rex by default, changeable later, with the URL rewrite handled for WordPress.
• A certificate, signed by your local CA, so the site opens on real HTTPS.
• A PHP version, switchable in one click without touching anything else.
• A web server — the shared nginx by default, or a per-site FrankenPHP or Apache override.
• A database, for site types that need one, with credentials rexenv manages.
• A log viewer, showing PHP, nginx and edge logs in one place.
• A terminal, opening in the docroot with the site’s own PHP and wp on PATH.
• Per-site environment variables.

Nothing here is decided permanently

PHP version, web server, database engine, domain, display name and docroot location can all be changed on an existing site. None of them require recreating it.

Renaming, moving, deleting

Action	What it changes	What it does not
Rename	The display name in the UI	The domain, the folder, anything on disk
Change domain	The domain and certificate, with a WordPress URL rewrite	Your files
Move	The docroot’s parent folder	The domain or the database
Delete	Drops the database and the docroot	A linked folder — never

rex site delete asks before it acts, and the app makes you type the domain: it is the one action here that destroys data.

Blueprints

A site you have set up the way you like can be saved as a blueprint, and new sites can be stamped from it. rex blueprints lists them; rex site create --blueprint <name> uses one.