Highlights

Two data-safety fixes for Deployments, both found while dogfooding 0.4.17:

Detect no longer erases your deployment config. Running Detect used to overwrite the server-side config blob with detection results only, silently dropping the saved Apply settings (preset, domain, git URL, SSL…) — which also made the Deploy button vanish. Detect now preserves the apply config, mirroring how Apply preserves detection results.
Re-apply now preserves storage/ too. 0.4.17 protected .env; this release extends the same protection to the whole storage/ directory (user uploads, logs). Re-provisioning a live site no longer destroys client-uploaded files.

What's fixed

Detect preserves the saved apply config — the PATCH sent after detection now carries the existing apply blob alongside the fresh detection results instead of replacing the whole config. Re-running Detect keeps the Deploy button, the chosen preset, and every Apply form value intact.
storage/ survives re-apply — before the wipe-and-clone, .env and storage/ are moved into a keep directory on the same filesystem (/var/www/.laraenv-keep-<name>), then restored over the fresh clone. Moving (not copying) means zero extra disk usage even for multi-GB storage dirs, and nothing lands in /tmp (often RAM-backed tmpfs).
Crash-safe keep-dir lifecycle — the keep directory is only removed after a successful clone + restore. If the clone fails midway (network drop, bad PAT), the preserved data stays put and the next Apply picks it up. Destroy removes the keep directory along with the deploy dir, so nothing is left behind. At most one keep dir exists per deployment (each backup replaces the previous one).
DB credentials are never rotated on re-apply anymore — with .env preserved, the MySQL bootstrap's idempotent fast path (existing credentials authenticate → skip) now actually triggers on re-apply, so the database user and password stay untouched.

Windows 10+ (x64) for the desktop app.
Cloud deploy targets: Ubuntu/Debian (apt-based).
No config or data migrations. Drop-in replacement for 0.4.17.
Note: deployments whose config was already lost to the Detect bug (config saved before 0.4.18, Detect re-run on 0.4.16/0.4.17) need their Apply form filled in once more — this release prevents the loss going forward but can't recover what the server already overwrote.