Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experience to be truly fulfilling. Laravel takes the pain out of development by easing common tasks used in many web projects, such as:
- Simple, fast routing engine.
- Powerful dependency injection container.
- Multiple back-ends for session and cache storage.
- Expressive, intuitive database ORM.
- Database agnostic schema migrations.
- Robust background job processing.
- Real-time event broadcasting.
Laravel is accessible, powerful, and provides tools required for large, robust applications.
Laravel has the most extensive and thorough documentation and video tutorial library of all modern web application frameworks, making it a breeze to get started with the framework.
You may also try the Laravel Bootcamp, where you will be guided through building a modern Laravel application from scratch.
If you don't feel like reading, Laracasts can help. Laracasts contains thousands of video tutorials on a range of topics including Laravel, modern PHP, unit testing, and JavaScript. Boost your skills by digging into our comprehensive video library.
We would like to extend our thanks to the following sponsors for funding Laravel development. If you are interested in becoming a sponsor, please visit the Laravel Partners program.
Thank you for considering contributing to the Laravel framework! The contribution guide can be found in the Laravel documentation.
In order to ensure that the Laravel community is welcoming to all, please review and abide by the Code of Conduct.
If you discover a security vulnerability within Laravel, please send an e-mail to Taylor Otwell via [email protected]. All security vulnerabilities will be promptly addressed.
The Laravel framework is open-sourced software licensed under the MIT license.
This project is configured to work with Postgres by default. For Neon (https://neon.tech) or any managed Postgres provider you should:
-
Create a Postgres database in your Neon dashboard and copy the connection string (DATABASE_URL). It looks like:
postgres://:@:/?sslmode=require
-
Add that value to your environment (for local development use your
.envfile):DATABASE_URL="postgres://user:password@...:5432/database?sslmode=require"
or set individual vars (DB_CONNECTION=pgsql, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, DB_PASSWORD) — but DATABASE_URL is recommended.
-
Run migrations and seeders using the Neon connection:
php artisan migrate --seed
Notes:
- Ensure
DB_SSLMODE(defaultrequire) matches the provider's requirement. Neon requires SSL connections. - Do not commit real credentials to the repo. Use environment variables or secret management in CI.
If you can't afford multiple databases (for example, on a hosted Postgres plan),
you can isolate tables for different apps by using an application-level table
prefix. Set the APP_DB_PREFIX environment variable (for example app1_) and
the application will automatically prepend that prefix to all table names and
to the migrations table. Example in your .env file:
APP_DB_PREFIX=app1_
Every table created by migrations will be named like app1_users,
app1_transactions, etc. Leave it empty for no prefix.