Recovery Page
The authenticated /recovery page provides maintenance and recovery tools for your GWM installation.
- Navigate to
/recoverywhile logged in as an admin. - If you cannot log in, verify that
APP_KEYand database credentials in.envare correct first. - The page uses the same shipped static assets as the rest of the application and includes plain recovery controls.
Environment Backups
GWM automatically backs up your application .env at key moments such as before self-updates. You can also create and restore backups manually at any time.
- Backups are listed in reverse-chronological order on the Recovery page.
- Click Restore next to a backup to replace the current
.envwith that snapshot. - Restoring does not restart the web server — clear the config cache or reload the server after restoring if settings do not take effect immediately.
- Click Delete to remove backups you no longer need.
- Use Create Backup before making bulk
.envchanges so you have a safe fallback.
Published Asset Repair
If static assets or cached Laravel files need repair after an update, use Repair Published Assets. This clears Laravel caches and republishes bundled assets without running npm.
- The action runs
php artisan optimize:clearand republishes Laravel package assets. - The page shows the latest repair log from
storage/logs/gwm-rebuild.log. - No
node_modules,public/build, Vite manifest, or npm binary is required for the GWM app UI. - Once complete, reload the main GWM URL to confirm the app is healthy.
When to Use Recovery
- After a self-update that leaves cached routes, views, or published assets stale.
- Before and after significant manual
.envchanges. - When rolling back a configuration change that caused errors.
- Before a major deployment or dependency upgrade as a precautionary snapshot.
See the Troubleshooting guide for step-by-step recovery walkthroughs.