{"id":476,"date":"2025-08-27T22:48:23","date_gmt":"2025-08-27T22:48:23","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=476"},"modified":"2025-08-27T22:48:25","modified_gmt":"2025-08-27T22:48:25","slug":"how-to-deploy-laravel-12-on-cpanel-hosting","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/how-to-deploy-laravel-12-on-cpanel-hosting\/","title":{"rendered":"How to Deploy Laravel 12 on cPanel Hosting"},"content":{"rendered":"\n

How to Deploy Laravel 12 on cPanel Hosting<\/strong><\/h2>\n\n\n\n

Not every project requires a VPS or cloud infrastructure. Many developers still rely on cPanel hosting<\/strong> for simplicity and cost-effectiveness. Deploying a Laravel 12 application on cPanel comes with its own challenges: shared servers, no SSH access in some cases, and the need to configure the public\/<\/code> folder properly. In this guide, we\u2019ll walk through a step-by-step approach to get your Laravel app running on a cPanel server with HTTPS, correct file permissions, and a clean URL structure.<\/p>\n\n\n\n

<\/div>\n\n\n\n

1 \u2014 Prepare Your Laravel Project<\/strong><\/h2>\n\n\n\n

Before uploading your application to cPanel, make sure you\u2019ve run composer and built your frontend assets locally:<\/p>\n\n\n

# From your local machine<\/span>\ncomposer install --optimize-autoloader --no-dev\nnpm install && npm run build\nphp artisan config:cache\nphp artisan route:cache\nphp artisan view:cache\nphp artisan migrate --force<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
This ensures your dependencies are installed, caches are built for performance, and your migrations are ready. Running --no-dev<\/code> keeps unnecessary dev packages out of production.<\/p>\n\n\n\n
<\/div>\n\n\n\n
2 \u2014 Upload to cPanel<\/strong><\/h2>\n\n\n\n
Most cPanel providers give you FTP or File Manager access. You should upload your entire Laravel project, but place the public\/<\/code> folder\u2019s contents into the public_html<\/code> directory.<\/p>\n\n\n
# Example structure after upload<\/span>\n\/home\/username\/\n  \u251c\u2500\u2500 laravel-app\/        # all Laravel files here<\/span>\n  \u2502   \u251c\u2500\u2500 app\/\n  \u2502   \u251c\u2500\u2500 bootstrap\/\n  \u2502   \u251c\u2500\u2500 config\/\n  \u2502   \u2514\u2500\u2500 ...\n  \u2514\u2500\u2500 public_html\/        # cPanel web root<\/span>\n      \u251c\u2500\u2500 index.php       # replaced with Laravel's public\/index.php<\/span>\n      \u251c\u2500\u2500 css\/\n      \u251c\u2500\u2500 js\/\n      \u2514\u2500\u2500 ...<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Instead of uploading the whole public\/<\/code> folder, move its contents into public_html<\/code>. Then, edit public\/index.php<\/code> to point to the correct paths for autoload.php<\/code> and app.php<\/code>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
3 \u2014 Update Index.php Paths<\/strong><\/h2>\n\n\n\n
After moving files, update the paths inside public_html\/index.php<\/code> so they point to the correct directory:<\/p>\n\n\n
\/\/ public_html\/index.php<\/span>\n\nrequire<\/span> __DIR__<\/span>.'\/..\/laravel-app\/vendor\/autoload.php'<\/span>;\n$app = require_once<\/span> __DIR__<\/span>.'\/..\/laravel-app\/bootstrap\/app.php'<\/span>;<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
By default, index.php<\/code> looks for ..\/vendor\/autoload.php<\/code>. Since we moved files into laravel-app\/<\/code>, update the paths accordingly. Without this, Laravel won\u2019t boot in production.<\/p>\n\n\n\n
<\/div>\n\n\n\n
4 \u2014 Configure .htaccess for Routing<\/strong><\/h2>\n\n\n\n
Laravel routes everything through public\/index.php<\/code>. Update the .htaccess<\/code> in public_html\/<\/code> to handle this properly:<\/p>\n\n\n
<IfModule mod_rewrite.c><\/span>\n    <IfModule mod_negotiation.c><\/span>\n        Options<\/span><\/span> -MultiViews -Indexes\n    <\/IfModule><\/span>\n\n    RewriteEngine<\/span><\/span> On<\/span>\n\n    # Redirect Trailing Slashes...<\/span>\n    RewriteCond<\/span><\/span> %{REQUEST_FILENAME}<\/span> !-d\n    RewriteRule<\/span><\/span> ^(.*)\/$ \/$1<\/span> [L,R=301]<\/span>\n\n    # Handle Front Controller...<\/span>\n    RewriteCond<\/span><\/span> %{REQUEST_FILENAME}<\/span> !-d\n    RewriteCond<\/span><\/span> %{REQUEST_FILENAME}<\/span> !-f\n    RewriteRule<\/span><\/span> ^ index.php [L]<\/span>\n<\/IfModule><\/span><\/code><\/span>Code language:<\/span> Apache<\/span> (<\/span>apache<\/span>)<\/span><\/small><\/pre>\n\n\n
This ensures that all requests are funneled through Laravel\u2019s front controller, while still serving static assets directly. For a similar setup on Nginx instead of cPanel\/Apache, check Laravel & Nginx: Best Practices for Production<\/a>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
5 \u2014 Configure Cron for Scheduler<\/strong><\/h2>\n\n\n\n
Laravel\u2019s task scheduler requires a cron job. You can set this in the cPanel > Cron Jobs section:<\/p>\n\n\n
* * * * * php \/home\/username\/laravel-app\/artisan schedule:run >> \/dev\/null 2>&1<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
6 \u2014 Secure Your Application<\/strong><\/h2>\n\n\n\n
cPanel hosting often comes with Apache and free SSL (via AutoSSL or Let\u2019s Encrypt). Make sure you force HTTPS and add security headers in your .htaccess<\/code> file.<\/p>\n\n\n
# Force HTTPS<\/span>\nRewriteEngine<\/span><\/span> On<\/span>\nRewriteCond<\/span><\/span> %{HTTPS}<\/span> !=on<\/span>\nRewriteRule<\/span><\/span> ^ https:\/\/%{HTTP_HOST}<\/span>%{REQUEST_URI}<\/span> [L,R=301]<\/span>\n\n# Security headers<\/span>\n<IfModule mod_headers.c><\/span>\n    Header<\/span><\/span> set X-Frame-Options \"SAMEORIGIN\"<\/span>\n    Header<\/span><\/span> set X-Content-Type-Options \"nosniff\"<\/span>\n    Header<\/span><\/span> set Referrer-Policy \"strict-origin-when-cross-origin\"<\/span>\n<\/IfModule><\/span><\/code><\/span>Code language:<\/span> Apache<\/span> (<\/span>apache<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
7 \u2014 Final Pre-Launch Checks<\/strong><\/h2>\n\n\n\n
Before going live, walk through this checklist:<\/p>\n\n\n\n
These rules ensure all traffic is encrypted and common browser security headers are applied. For more on security, check How to Prevent CSRF, XSS, and SQL Injection in Laravel Apps<\/a>.<\/p>\n\n\n\n
This runs the Laravel scheduler every minute, which then executes scheduled tasks as defined in app\/Console\/Kernel.php<\/code>. For a production-grade queue and scheduling setup, see How to Use Laravel Queues for Faster Performance<\/a>.<\/p>\n\n\n\n