A development server is a convenience for you. It is not a deployment, and a portfolio that only runs on your laptop cannot be reviewed by anyone.
Most hosting sold in Bangladesh is cPanel shared hosting, so that is what this covers. These are the steps tutorials skip.
1. The document root is the whole problem
Laravel expects the web server to serve its public/ folder and nothing else. Shared hosting serves public_html/.
Upload the application outside public_html — a sibling folder such as laravelapp/ — then put the contents of the project's public/ folder into public_html/, and edit the two paths at the top of index.php to point at the folder you created.
Do not shortcut this by uploading everything into public_html. If you do, your .env file — database password included — is reachable in a browser.
2. Check the PHP version before anything else
In cPanel, open MultiPHP Manager and look at what is actually selected for your domain. Shared hosts frequently default to an old version, and a recent Laravel will not run on it at all.
This is worth doing first, because the error it produces is an unhelpful blank page, and people lose hours to it after everything else is already correct.

3. Permissions on two folders
storage/ and bootstrap/cache/ must be writable by the web server. If they are not, you get a 500 with nothing useful on screen.
Set them to 755 first. Use 775 only if your host requires it, and never 777 — that is world-writable, and on shared hosting "world" includes other customers.
4. The .env file, and the key
Copy .env.example to .env, fill in the database name, user and password that cPanel gave you, and set APP_DEBUG=false.
That last one matters more than it looks. With debug on, any error page prints your configuration — including credentials — to whoever triggered it. Leaving it on is the most common security mistake in a student deployment.
You also need APP_KEY set. If you cannot run php artisan key:generate on the server, generate it locally and paste the value in.
5. Composer, when there is no terminal
Many shared plans have no SSH. Run composer install --no-dev --optimize-autoloader on your own machine and upload the resulting vendor/ folder with everything else.
It is a large upload over a slow connection, which is unpleasant, but it works on hosting where nothing else will.
6. The scheduler needs a cron entry
If your application schedules anything, add one cron job in cPanel running every minute, pointing at artisan schedule:run with the full path to the PHP binary your host uses — not just php, which on shared hosting often resolves to the wrong version.
When it still shows a blank page
A white screen is almost always one of four things: the PHP version, the two folder permissions, a missing APP_KEY, or vendor/ not uploaded. Check them in that order.
Read the real error in storage/logs/laravel.log rather than guessing. And if the host's own error log is available in cPanel, read that too — a permissions failure often appears there and nowhere else.
Once the site answers on a real domain, you have the thing part one was for: a URL you can put on a CV that a stranger can open.
Part four, tomorrow: what a reviewer looks at in your GitHub profile, and in what order.




