[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-host-laravel-plesk":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":21,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fcloud\u002Fhebergement-web\u002Fhost-laravel-plesk","host-laravel-plesk","How to Host a Laravel Website on Plesk","Host your Laravel application on Winheberg Plesk web hosting with Laravel Toolkit, skeleton or Git repository, production .env, MySQL database, scheduled tasks and deployment.","cloud","hebergement-web","tabler:file-text","2026-11-01","Winheberg",133,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk.webp",[16,17,18,19,20],"Laravel","Plesk","PHP","Deployment","Web Hosting",[22,23,24,25,26,27],"host laravel","laravel plesk","laravel toolkit","deploy laravel","laravel php hosting","laravel production","","\u002Fdocs\u002Fhebergement-web\u002Fheberger-laravel-plesk","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>Laravel is a widely used PHP framework for building websites and web applications, from an API to a full back office. It relies on Composer for its dependencies, on Artisan for its commands and on an \u003Ccode>.env\u003C\u002Fcode> file for its configuration.\u003C\u002Fp>\n\u003Cp>Your \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fcloud\u002Fweb-hosting\">Winheberg web hosting\u003C\u002Fa> includes Laravel Toolkit, a Plesk extension dedicated to this framework. It installs a new project or fetches yours from a Git repository, installs the Composer dependencies and sets the website root to the \u003Ccode>public\u003C\u002Fcode> folder, so the source code and the \u003Ccode>.env\u003C\u002Fcode> file stay out of reach from the web.\u003C\u002Fp>\n\u003Cp>This guide covers the installation, the switch to production, the database, scheduled tasks and the deployment of updates.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The Winheberg Plesk panel is displayed in French. Menu, field and button names are quoted below exactly as they appear on screen, followed by their English meaning.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A Winheberg web hosting plan with access to the Plesk panel\u003C\u002Fli>\n\u003Cli>A domain or subdomain added in Plesk, see our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fconnect-external-domain-plesk\">How to Connect an External Domain to Your Plesk Hosting\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>For an existing project, its Git repository on GitHub, GitLab, Bitbucket or your own server\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Laravel Toolkit moves the website root to the application \u003Ccode>public\u003C\u002Fcode> folder. Dedicate a domain or subdomain to your Laravel application, for instance \u003Ccode>app.example.com\u003C\u002Fcode>, rather than installing over an existing website.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Open Laravel Toolkit\u003C\u002Fh2>\n\u003Cp>In \u003Cstrong>Sites Web &amp; Domaines\u003C\u002Fstrong> (\u003Cem>Websites &amp; Domains\u003C\u002Fem>), open your domain, then the \u003Cstrong>Démarrer\u003C\u002Fstrong> (\u003Cem>Get Started\u003C\u002Fem>) tab. Click \u003Cstrong>Laravel\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572336253-c6e3150d65f140eca311ab96.webp\" alt=\"Get Started tab of a Plesk domain with the Laravel entry\" width=\"540\" \u002F>\n\n\u003Cp>You also reach Laravel Toolkit through the \u003Cstrong>Laravel\u003C\u002Fstrong> entry of the side menu. As long as no application exists, the page offers \u003Cstrong>Installer l&#39;application\u003C\u002Fstrong> (\u003Cem>Install Application\u003C\u002Fem>) and \u003Cstrong>Analyser\u003C\u002Fstrong> (\u003Cem>Scan\u003C\u002Fem>), the latter finding a Laravel application already present on your domains. Click \u003Cstrong>Installer l&#39;application\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572336664-d39785b1bea2e2af797eb34f.webp\" alt=\"Plesk Laravel Toolkit page with the Install Application button\" width=\"800\" \u002F>\n\n\u003Ch2>2. Choose the application source\u003C\u002Fh2>\n\u003Cp>In the \u003Cstrong>Installer l&#39;application\u003C\u002Fstrong> window, pick your domain in \u003Cstrong>Choisissez un domaine\u003C\u002Fstrong> (\u003Cem>Choose a domain\u003C\u002Fem>), then pick one of the two sources offered.\u003C\u002Fp>\n\u003Ch3>Start a new project\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Installer le squelette\u003C\u002Fstrong> (\u003Cem>Install skeleton\u003C\u002Fem>) creates a blank Laravel application, along with a local Git repository hosted by Plesk. It is the right choice to start a project or try the framework.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572336968-33d603c7c90db6b2d3cecebd.webp\" alt=\"Domain choice and Install skeleton in Laravel Toolkit\" width=\"790\" \u002F>\n\n\u003Ch3>Deploy an existing project\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Installer depuis un dépôt distant\u003C\u002Fstrong> (\u003Cem>Install from a remote repository\u003C\u002Fem>) fetches your code from a Git service. Enter the repository address in the \u003Cstrong>Dépôt\u003C\u002Fstrong> (\u003Cem>Repository\u003C\u002Fem>) field.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572337425-715eaf8849412644f92fc0ce.webp\" alt=\"Installation from a remote Git repository and SSH public key in Laravel Toolkit\" width=\"790\" \u002F>\n\n\u003Cp>For a public repository, its HTTPS address is enough. For a private repository, enter its SSH address, such as \u003Ccode>git@github.com:your-account\u002Fyour-project.git\u003C\u002Fcode>, then add the key shown in \u003Cstrong>Clé publique SSL\u003C\u002Fstrong> (\u003Cem>SSH public key\u003C\u002Fem>) to the repository deploy keys. On GitHub, they sit in the repository \u003Cstrong>Settings\u003C\u002Fstrong>, \u003Cstrong>Deploy keys\u003C\u002Fstrong> section, and on GitLab in \u003Cstrong>Settings\u003C\u002Fstrong>, \u003Cstrong>Repository\u003C\u002Fstrong>, \u003Cstrong>Deploy keys\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>A deploy key grants access to a single repository, read-only by default. It is safer than adding the key to your account, which would open all your repositories.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>3. Follow the installation\u003C\u002Fh2>\n\u003Cp>Confirm the window. Laravel Toolkit shows the progress in \u003Cstrong>Déploiement du projet\u003C\u002Fstrong> (\u003Cem>Project deployment\u003C\u002Fem>), from the Git repository creation to the Composer dependencies, then the hosting and PHP configuration. Allow a few minutes.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572337827-c9002e40d402a2d81f96cf27.webp\" alt=\"Laravel project deployment window in Plesk\" width=\"490\" \u002F>\n\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The skeleton installs Laravel 13, which requires PHP 8.3 or later. For an existing project, check that the domain PHP version, shown in \u003Cstrong>Paramètres PHP\u003C\u002Fstrong> (\u003Cem>PHP Settings\u003C\u002Fem>), matches the one your \u003Ccode>composer.json\u003C\u002Fcode> file requires.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>4. Discover the dashboard\u003C\u002Fh2>\n\u003Cp>Once the installation is done, Laravel Toolkit opens the \u003Cstrong>Application Laravel\u003C\u002Fstrong> page of your domain. The \u003Cstrong>Tableau de bord\u003C\u002Fstrong> (\u003Cem>Dashboard\u003C\u002Fem>) shows the website URL, the \u003Cstrong>Dépôt\u003C\u002Fstrong> (\u003Cem>Repository\u003C\u002Fem>) address and the \u003Cstrong>Dernier commit\u003C\u002Fstrong> (\u003Cem>Latest commit\u003C\u002Fem>). The \u003Cstrong>Artisan\u003C\u002Fstrong>, \u003Cstrong>Composer\u003C\u002Fstrong>, \u003Cstrong>Node.js\u003C\u002Fstrong>, \u003Cstrong>Déploiement\u003C\u002Fstrong> (\u003Cem>Deployment\u003C\u002Fem>) and \u003Cstrong>File d&#39;attente\u003C\u002Fstrong> (\u003Cem>Queue\u003C\u002Fem>) tabs group the application tools.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572338234-94440a6403b8cbfec345b7a8.webp\" alt=\"Laravel Toolkit dashboard with its tabs and settings\" width=\"790\" \u002F>\n\n\u003Cp>For a skeleton installation, the \u003Cstrong>Dépôt\u003C\u002Fstrong> field shows the address of the local Git repository created by Plesk, where you can push your code. The \u003Cstrong>Journaux\u003C\u002Fstrong> (\u003Cem>Logs\u003C\u002Fem>) link on the left displays the application logs.\u003C\u002Fp>\n\u003Ch2>5. Switch the application to production\u003C\u002Fh2>\n\u003Cp>The skeleton starts in development mode. Open the \u003Cstrong>Artisan\u003C\u002Fstrong> tab, type \u003Ccode>about\u003C\u002Fcode> in the \u003Cstrong>php artisan\u003C\u002Fstrong> field and confirm. The command shows the \u003Cstrong>Environment\u003C\u002Fstrong> as \u003Ccode>local\u003C\u002Fcode>, the \u003Cstrong>Debug Mode\u003C\u002Fstrong> as \u003Ccode>ENABLED\u003C\u002Fcode> and a \u003Ccode>localhost\u003C\u002Fcode> \u003Cstrong>URL\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572338623-66de936166162bbe5066a628.webp\" alt=\"php artisan about command in the Laravel Toolkit Artisan tab\" width=\"790\" \u002F>\n\n\u003Cdiv class=\"markdown-alert markdown-alert-caution\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12.01\" y2=\"16\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>In debug mode, any error shows visitors a detailed page that may reveal your code, your paths and your settings. Turn it off before opening the website to the public.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>Go back to the \u003Cstrong>Tableau de bord\u003C\u002Fstrong> and click \u003Cstrong>Éditer\u003C\u002Fstrong> (\u003Cem>Edit\u003C\u002Fem>) next to \u003Cstrong>Variables d&#39;environnement (.env)\u003C\u002Fstrong> (\u003Cem>Environment variables\u003C\u002Fem>). The \u003Cstrong>Modifier .env\u003C\u002Fstrong> (\u003Cem>Edit .env\u003C\u002Fem>) editor opens.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572339031-44dbc700811e96f9ff273b74.webp\" alt=\"Laravel .env file set for production in Plesk\" width=\"600\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Values to set for production\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Variable\u003C\u002Fth>\n\u003Cth>Value\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Ccode>APP_ENV\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>production\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>APP_DEBUG\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>false\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>APP_URL\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Your website address, for instance \u003Ccode>https:\u002F\u002Fapp.example.com\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">Never change APP_KEY, generated during installation, or sessions and encrypted data become unreadable.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>Save, then run \u003Ccode>about\u003C\u002Fcode> again in the \u003Cstrong>Artisan\u003C\u002Fstrong> tab to check that the \u003Cstrong>Environment\u003C\u002Fstrong> shows \u003Ccode>production\u003C\u002Fcode> and the \u003Cstrong>Debug Mode\u003C\u002Fstrong> shows \u003Ccode>OFF\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2>6. Connect a database\u003C\u002Fh2>\n\u003Cp>The skeleton uses SQLite, a database stored in a single project file, with \u003Ccode>DB_CONNECTION=sqlite\u003C\u002Fcode>. It is enough for a small website. For MySQL or MariaDB, first create a database in \u003Cstrong>Bases de données\u003C\u002Fstrong> (\u003Cem>Databases\u003C\u002Fem>), \u003Cstrong>Ajouter une base de données\u003C\u002Fstrong> (\u003Cem>Add Database\u003C\u002Fem>), noting its full name, its user and its password.\u003C\u002Fp>\n\u003Cp>In \u003Cstrong>Modifier .env\u003C\u002Fstrong>, replace the \u003Ccode>DB_CONNECTION=sqlite\u003C\u002Fcode> line with the block below. If the \u003Ccode>DB_HOST\u003C\u002Fcode> to \u003Ccode>DB_PASSWORD\u003C\u002Fcode> lines are already there as comments, starting with a \u003Ccode>#\u003C\u002Fcode>, replace them too so they are not duplicated.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-ini\">DB_CONNECTION=mysql\nDB_HOST=localhost\nDB_PORT=3306\nDB_DATABASE=full_database_name\nDB_USERNAME=database_user\nDB_PASSWORD=database_password\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Then create the tables from the \u003Cstrong>Artisan\u003C\u002Fstrong> tab with the following command. The \u003Ccode>--force\u003C\u002Fcode> option is required in production, otherwise Laravel refuses to run migrations without confirmation.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">migrate --force\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>7. Schedule Laravel tasks\u003C\u002Fh2>\n\u003Cp>If your application uses the Laravel scheduler, defined in \u003Ccode>routes\u002Fconsole.php\u003C\u002Fcode>, it must be called every minute. The \u003Cstrong>Tâches planifiées\u003C\u002Fstrong> (\u003Cem>Scheduled tasks\u003C\u002Fem>) and \u003Cstrong>File d&#39;attente\u003C\u002Fstrong> (\u003Cem>Queue\u003C\u002Fem>) switches of the dashboard require SSH access to the hosting. When it is forbidden, as the \u003Cstrong>Accès SSH\u003C\u002Fstrong> (\u003Cem>SSH access\u003C\u002Fem>) line of the \u003Cstrong>Paramètres d&#39;hébergement\u003C\u002Fstrong> (\u003Cem>Hosting Settings\u003C\u002Fem>) shows, they stay greyed out. Create the task directly in Plesk instead, it works without SSH.\u003C\u002Fp>\n\u003Cp>From the domain \u003Cstrong>Tableau de bord\u003C\u002Fstrong>, \u003Cstrong>Outils Dévelop.\u003C\u002Fstrong> (\u003Cem>Dev Tools\u003C\u002Fem>) section, open \u003Cstrong>Tâches planifiées\u003C\u002Fstrong> (\u003Cem>Scheduled Tasks\u003C\u002Fem>), then click \u003Cstrong>Ajouter une tâche\u003C\u002Fstrong> (\u003Cem>Add Task\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793569975011-f2e0acca7249229cdf0e83b3.webp\" alt=\"Plesk scheduled task running artisan schedule:run every minute\" width=\"770\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Scheduled task settings\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field on screen\u003C\u002Fth>\n\u003Cth>Value\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Type de tâche (\u003Cem>Task type\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Exécuter un script PHP\u003C\u002Fstrong> (\u003Cem>Run a PHP script\u003C\u002Fem>)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Chemin d&#39;accès du script (\u003Cem>Script path\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The application folder followed by \u003Ccode>\u002Fartisan\u003C\u002Fcode>, for instance \u003Ccode>app.example.com\u002Fartisan\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>avec arguments (\u003Cem>with arguments\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>schedule:run\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Utiliser la version de PHP (\u003Cem>Use PHP version\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The same version as the website\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Exécuter (\u003Cem>Run\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Style Cron\u003C\u002Fstrong> (\u003Cem>Cron style\u003C\u002Fem>), with \u003Ccode>* * * * *\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>The application folder is the one in \u003Cstrong>Racine du document\u003C\u002Fstrong> (\u003Cem>Document root\u003C\u002Fem>), without the trailing \u003Ccode>\u002Fpublic\u003C\u002Fcode>. You find it in the \u003Cstrong>Hébergement et DNS\u003C\u002Fstrong> (\u003Cem>Hosting &amp; DNS\u003C\u002Fem>) tab, \u003Cstrong>Hébergement\u003C\u002Fstrong> (\u003Cem>Hosting\u003C\u002Fem>) entry.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If your application pushes jobs to a queue, add a second identical task with the \u003Ccode>queue:work --stop-when-empty\u003C\u002Fcode> argument. It processes pending jobs every minute, then stops.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>8. Deploy your updates\u003C\u002Fh2>\n\u003Cp>The \u003Cstrong>Déploiement\u003C\u002Fstrong> (\u003Cem>Deployment\u003C\u002Fem>) tab sets how new code reaches production. In \u003Cstrong>Manuel\u003C\u002Fstrong> (\u003Cem>Manual\u003C\u002Fem>) mode, nothing changes on the website until you click \u003Cstrong>Déployer\u003C\u002Fstrong> (\u003Cem>Deploy\u003C\u002Fem>). In \u003Cstrong>Automatique\u003C\u002Fstrong> (\u003Cem>Automatic\u003C\u002Fem>) mode, deployment starts by itself on each new push to the local repository, or when the webhook is called for a remote repository.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572339420-409e0496f5d205c0594685fe.webp\" alt=\"Laravel Toolkit Deployment tab with the Deploy button\" width=\"790\" \u002F>\n\n\u003Cp>The \u003Cstrong>Étapes du déploiement\u003C\u002Fstrong> (\u003Cem>Deployment steps\u003C\u002Fem>) run in the order shown. Greyed out steps are mandatory, the others are ticked according to your project, for instance \u003Cstrong>Installer les package.json dépendances\u003C\u002Fstrong> (\u003Cem>Install package.json dependencies\u003C\u002Fem>) if your website builds its assets with npm. Editing the \u003Cstrong>Script de déploiement\u003C\u002Fstrong> (\u003Cem>Deployment script\u003C\u002Fem>) also requires SSH access.\u003C\u002Fp>\n\u003Cp>After a deployment that adds migrations, run \u003Ccode>migrate --force\u003C\u002Fcode> from the \u003Cstrong>Artisan\u003C\u002Fstrong> tab.\u003C\u002Fp>\n\u003Ch2>9. Open your website\u003C\u002Fh2>\n\u003Cp>Open your domain in a browser. For a skeleton, the Laravel welcome page is displayed.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-laravel-plesk-1793572339788-2916512069ce7eb268d673e9.webp\" alt=\"Default Laravel 13 welcome page\" width=\"680\" \u002F>\n\n\u003Cp>To serve the application over HTTPS, install the free certificate with our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk\">How to Generate a Let&#39;s Encrypt SSL Certificate for Your Website\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The website shows a 500 error without details\u003C\u002Fh3>\n\u003Cp>This is the normal behaviour in production, the error details go to the logs.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Open the \u003Cstrong>Journaux\u003C\u002Fstrong> (\u003Cem>Logs\u003C\u002Fem>) link of Laravel Toolkit, or the \u003Ccode>storage\u002Flogs\u002Flaravel.log\u003C\u002Fcode> file in the file manager\u003C\u002Fli>\n\u003Cli>If the message says \u003Ccode>No application encryption key has been specified.\u003C\u002Fcode>, run \u003Ccode>key:generate --force\u003C\u002Fcode> from the \u003Cstrong>Artisan\u003C\u002Fstrong> tab\u003C\u002Fli>\n\u003Cli>If the error comes from the database, check the \u003Ccode>DB_\u003C\u002Fcode> lines of the \u003Ccode>.env\u003C\u002Fcode> file\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ A change to .env is not applied\u003C\u002Fh3>\n\u003Cp>The configuration has been cached, Laravel no longer reads the \u003Ccode>.env\u003C\u002Fcode> file.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Run \u003Ccode>config:clear\u003C\u002Fcode> from the \u003Cstrong>Artisan\u003C\u002Fstrong> tab\u003C\u002Fli>\n\u003Cli>If you use \u003Ccode>optimize\u003C\u002Fcode> during your deployments, run it again after each \u003Ccode>.env\u003C\u002Fcode> change\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The remote repository refuses the connection\u003C\u002Fh3>\n\u003Cp>Laravel Toolkit cannot authenticate with your Git service.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>For a private repository, check that you entered the SSH address, \u003Ccode>git@...\u003C\u002Fcode>, and not the HTTPS one\u003C\u002Fli>\n\u003Cli>Check that the key shown in \u003Cstrong>Clé publique SSL\u003C\u002Fstrong> is listed in the repository deploy keys\u003C\u002Fli>\n\u003Cli>Copy the whole key, from the leading \u003Ccode>ssh-rsa\u003C\u002Fcode> to the last character\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Migrations fail\u003C\u002Fh3>\n\u003Cp>Laravel cannot connect to the database or refuses to run the command.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Add the \u003Ccode>--force\u003C\u002Fcode> option, without it migrations do not run in production\u003C\u002Fli>\n\u003Cli>An \u003Ccode>Access denied\u003C\u002Fcode> message points to a wrong user name or password in \u003Ccode>.env\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Check that \u003Ccode>DB_DATABASE\u003C\u002Fcode> holds the full database name, prefix included\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Keep \u003Ccode>APP_DEBUG=false\u003C\u002Fcode> on the public website, and test your changes on a staging subdomain\u003C\u002Fli>\n\u003Cli>Never commit the \u003Ccode>.env\u003C\u002Fcode> file, the \u003Ccode>.gitignore\u003C\u002Fcode> shipped with Laravel already excludes it\u003C\u002Fli>\n\u003Cli>Stay in \u003Cstrong>Manuel\u003C\u002Fstrong> deployment mode as long as you have no automated tests\u003C\u002Fli>\n\u003Cli>Keep the \u003Cstrong>Activer le mode Maintenance\u003C\u002Fstrong> (\u003Cem>Enable maintenance mode\u003C\u002Fem>) step ticked, your visitors see a waiting page rather than a half-updated website\u003C\u002Fli>\n\u003Cli>Export your database before any significant migration\u003C\u002Fli>\n\u003Cli>To give a developer access without sharing your account, follow our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fcreate-user-account-plesk\">How to Create a User in Plesk\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If the installation fails or your application will not start on your hosting, open a ticket with our support from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, \u003Cstrong>Technical\u003C\u002Fstrong> department, filling in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the web hosting concerned. For questions about the framework itself, see the \u003Ca href=\"https:\u002F\u002Flaravel.com\u002Fdocs\">official Laravel documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Your Laravel application runs in production, ready to welcome its first users 🚀\u003C\u002Fp>\n",1794526350750]