Create from a git repository

Available for Laravel and blank PHP sites. Give rexenv a repository URL and it clones it, provisions the site around it, and runs the setup a fresh checkout needs.

What it runs

For a Laravel project, three commands, named on the dialog above the Create button before you press it:

composer install
php artisan key:generate
php artisan migrate

This runs the repository's own code

composer install executes whatever install scripts the project declares, and migrate writes to the database. That is not a rexenv behaviour — it is what setting up a PHP project means — but it is your decision to make, which is why the sentence naming those three commands sits in front of the button that starts them rather than in a doc you might read afterwards.

Why composer install has no opt-out

vendor/ is gitignored in essentially every PHP project, so a checkout without it does not run. Offering to skip the step would be offering to create a site that 500s on the first request — an option whose only outcome is a broken site is a trap, not a choice.

Private repositories

Cloning uses your own ssh keys, the same ones your terminal uses. rexenv does not ask for a token, does not store credentials, and does not proxy the clone through anything.

Public repos work over https or as owner/repo.

Why not WordPress

A WordPress repository without its database is not a site — it is a folder of PHP files that redirects to an installer. The backend refuses the combination, and the New Site dialog does not offer From Git for WordPress rather than drawing a button that leads to a refusal.

To bring an existing WordPress project across, link the folder and import its database, or use the Valet/Herd migration if it lives in one of those.

Adding plugins and themes from git

Separate feature, same idea, scoped to an existing WordPress site: repo add clones a plugin or theme into wp-content, with branch switching, PR refs, dependency checks and dev watchers. See the CLI reference.