Danger
Back up and rehearse first. Package updates can overwrite modified product files. Keep customizations under version control and test the new release on staging.
- Read the release notes and compare new requirements with your server.
- Back up the database,
.env, storage, and customizations. - Enable maintenance mode or otherwise prevent writes while replacing application files.
- Download the latest Envato archive and replace the application with the contents of its
Scriptdirectory. Preserve your.envand required persistent storage. - Visit
https://your-domain.example/updatewhile signed in as an administrator and complete the database update wizard. - Clear application caches if the release notes require it and restart every queue worker.
- Disable maintenance mode and run the launch smoke test: login, email, storage, AI, integration, queued flow, webhook, scheduled flow, approval, and payment callback.
If the installer appears after an update, confirm storage/app/installed was preserved. If the application fails before the update wizard loads, inspect storage/logs/laravel.log, PHP compatibility, file ownership, the restored .env, and whether the complete vendor/ directory was uploaded.