Plesk's Laravel Toolkit makes it easy to deploy and manage Laravel applications directly from your hosting panel — no command line needed for most tasks.
Prerequisites
- The Laravel Toolkit extension must be installed on the server. If you don't see the Laravel option, contact your hosting provider.
- A domain or subdomain set up in Plesk to host your application.
Option 1: Install a fresh Laravel skeleton
- Log in to Plesk.
- Go to Websites & Domains and find your domain.
- Click Create Website > Laravel.
- Select Install Skeleton and click Install Application.
- Wait for the installation to complete — your Laravel app is now live.
Option 2: Deploy from a Git repository
- Follow steps 1–3 above.
- Select Install from remote repository.
- Paste your Git repository URL.
- If the repository is private, add the displayed public key to your repository deploy keys.
- Click Install Application.
Option 3: Upload existing files and scan
- Upload your Laravel project files to the domain directory via File Manager or FTP.
- Go to Websites & Domains > your domain > Hosting & DNS tab > Hosting.
- Change Document root to your app
publicdirectory (e.g./httpdocs/public) and click Save. - Go back to the Dashboard tab, click Create Website > Laravel, click Cancel, then click Scan.
Setting up a database
- From the Laravel dashboard, click Manage domain.
- Click Databases > Add Database and create your database.
- Go back to the domain card and click Laravel.
- Click Edit next to "Environment variables (.env)" and add your database credentials.
- Go to the Artisan tab and run the
migratecommand.
Running commands
The Laravel Toolkit lets you run Artisan, Composer, and npm commands directly from Plesk — no SSH required. Switch to the relevant tab and select or type your command.
Troubleshooting
- Laravel option missing: The Laravel Toolkit extension is not installed. Contact your hosting provider.
- 500 error after deployment: Check your
.envfile for correct database credentials and runartisan config:cache. - Permission errors: Make sure the
storageandbootstrap/cachedirectories are writable.