Updating

Homebrew

brew update && brew upgrade --cask rexenv

Disk image

Quit rexenv, then drag the new copy over the old one in Applications.

The Gatekeeper right-click → Open step is only needed the first time you ever install — an update over an app you have already approved opens normally.

What survives an update

Everything that matters:

• Your sites, their files and their databases
• Downloaded components — nothing re-downloads
• Settings, blueprints, certificates and CA trust
• The resolver files and the edge daemon

They live in ~/Library/Application Support/dev.rexenv.rexenv/ and in the system locations listed under Where things live, not inside the app bundle.

Quit before updating

Replacing the bundle under a running app is the usual way to get strange behaviour until the next launch. rexenv’s services outlive the app deliberately, so quitting it does not stop your sites — the update is genuinely just swapping the bundle.

Component versions do not change on their own

Updating rexenv can bring new pinned versions of PHP, nginx or a database engine. Those are part of the release, listed in its notes, and never a background download that changes your stack while you are working — see Pinned versions.

A new PHP minor becoming available does not switch any existing site to it.

Checking what you have

rex version

Prints the app and CLI versions. They should match; a mismatch usually means an old rex is earlier on your PATH than the one the current install linked.