0% found this document useful (0 votes)
40 views

Public: - : Top Level Folder: App

The document outlines the folder structure and purpose of key folders in a Laravel application. The top level folders are App, Public, and Vendor. App contains controllers, models, views and assets. Public is the web server document root and contains front-end assets. Vendor holds third-party code. Key subfolders of App include Config for application settings, Database for migrations and seeds, and Models for representing application data.

Uploaded by

Arfan Hassan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
40 views

Public: - : Top Level Folder: App

The document outlines the folder structure and purpose of key folders in a Laravel application. The top level folders are App, Public, and Vendor. App contains controllers, models, views and assets. Public is the web server document root and contains front-end assets. Vendor holds third-party code. Key subfolders of App include Config for application settings, Database for migrations and seeds, and Models for representing application data.

Uploaded by

Arfan Hassan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Top level folder:

App: -

Contains the controllers, models, views and assets for your application. This is where the
majority of the code for your application will live. You will be spending most of your time in this
folder!
Public: The only folder seen to the world as-is. This is the directory that you have to point your web
server to. It contains the bootstrap file index. Php which jump-starts the Laravel framework
core. The public directory can also be used to hold any publicly accessible static assets such as
CSS, JavaScript files, images and other files.
Vendor: A place for all third-party code. In a typical Laravel application, this includes the Laravel source
code and its dependencies, and plugins containing additional prepackaged functionality.
app/config/

Configure your applications runtime rules, database, session and more. Contains a number of
config files for changing various aspects of the framework. Most of the config files return
associative PHP arrays of options.
app/config/app.php

Configuration for various application level settings, i.e. timezone, locale, debug mode and
unique encryption key.
app/config/auth.php

Configuration that controls how user authentication will be performed in the application, i.e.
authentication driver.
app/config/cache.php

If the application utilizes caching to speed up response time, this is where you configure the
feature.
app/config/database.php

Contains relevant configuration information for the database, i.e. default database engine and
connection information.
app/config/session.php

Configuration that controls how user sessions are managed by Laravel, i.e. session driver,
session lifetime.
app/config/view.php

Misc. configuration settings for templating systems.


app/controllers

Contains the controller classes that are used to provide basic logic, interact with data models,
and load view files for your application.
app/database/migrations/

The migrations folder contains PHP classes which allow Laravel to update the Schema of your
current database while keeping all versions of the database in sync. Migration files are
generated using the Artisan tool.
app/database/seeds/

The seeds folder contains PHP files which allow Artisan to populate database tables with
reference data.
app/models/

Models are classes that represent the information (data) of the application and the rules to
manipulate that data. In most cases, each table in your database will correspond to one model
in your application. The bulk of your applications business logic will be concentrated in the
models.
app/start/

Contains custom settings related to the artisan tool as well as global and local context.
app/storage/

The storage directory is used as temporary file store for various Laravel services such as
sessions, cache, compiled view templates. This directory must be writable by the web server.
This directory is maintained by Laravel and you need not tinker with it.

You might also like