What this screen does
The Deploy page installs your generated application on a server you control. You register an SSH target, test the connection, and start a deployment run that the page tracks through every step — from preflight checks to a verified, running application.
Typical workflow
- Add a deployment target: host, port, user, and credentials for a server you administer. Targets are saved per project, and Test connection confirms the platform can reach it before anything is installed.
- Optionally enable demo data so the deployed app starts with realistic example records instead of empty tables.
- Start the deployment. The timeline walks through the steps live: preflight, build artifact, upload, provision, overlay, configure, migrate, publish, verify.
- If a step fails, the timeline shows where and why; fix the cause (often server-side) and resume from that step rather than starting over.
- When the run verifies, your application is live on your server.
Examples & tips
- Deploy only to servers you own or administer — the run installs software, writes configuration, and runs migrations.
- The most common first-run failures are server-side prerequisites (PHP version, database access, permissions); the preflight step is designed to catch them before anything is changed.
- Prefer to deploy by hand? Download the archive from the Laravel tab and follow the Deployment Guide instead — the result is the same application.