در حال بارگذاری ...

Composer vs laravel new0:01

Starting from Laravel 11, whenever you create a Laravel project using composer create-project, when that application is constructed, it's actually going to install a SQLite database for you during installation, and it will migrate the database right off the bat, without you doing any configuration. Of course, that's incredibly easy to change. All we have to do is go into the .env file in our project, and from there we can switch this to MySQL, uncomment these lines, and we're good to go. This only applies to the composer command, because if you use the laravel new command, well, it's going to ask you which database connection you'd like to set up anyway. For me, this illustrates the entire ethos of Laravel 11. It stops you worrying about configuration. It makes you productive right out of the box, and allows you to start creating much faster than you could in previous versions.

Laravel 11 Productivity Ethos0:52

It stops you worrying about configuration. It makes you productive right out of the box, and allows you to start creating much faster than you could in previous versions.

دوست دارید گاهی خبرهای Laracasts را ایمیل کنیم؟