Knowledgebase

Understanding the Laravel Project Structure Print

  • phplaravel, migration, caching, cpanel, database, webhosting, uploads, guide
  • 0

Where things live.

WHAT THE MAIN DIRECTORIES HOLD

Application code: controllers, models, and your own classes

Configuration Database migrations and seed data Public files, including the single entry point Templates Route definitions

Generated files: cache, logs, compiled templates, uploads

Dependencies, installed by Composer Tests

WHAT MATTERS MOST ABOUT THAT LIST

Only one directory is meant to be publicly reachable.

Everything else sits outside it.

WHY

So configuration, code and data cannot be requested directly.

WHAT THAT MEANS ON SHARED HOSTING

The default arrangement must be adapted, since cPanel serves a specific directory.

WHAT THE ENTRY POINT DOES

Receives every request and passes it to the framework.

WHAT THE COMMAND-LINE TOOL PROVIDES

Generating files, running migrations, clearing caches, running scheduled work.

WHAT TO KEEP OUT OF VERSION CONTROL

Dependencies Environment configuration Generated files

WHAT TO LEARN EARLY

Where to look when something is wrong: the log directory.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot