Laravel 11: A new streamlined directory structure!

Подписаться 24 тыс.

Просмотров 21 тыс.

50% 1

You’ll love the slim application skeleton you start with in a new Laravel 11 app! Newcomers will appreciate the minimalism, and experienced developers upgrading will not experience breaking changes.
Video Links:
➫ New directory structure: laravel-news.com/laravel-11-d...
➫ Laravel 11 overview: laravel-news.com/laravel-11
➫ Laravel Shift: laravelshift.com/
➫ Laravel 11 Playlist: • Laravel 11 will have n...
⏰ Timestamps: Laravel 11: New Streamlined Application Skeleton
0:00 - Laravel 11 introduction
0:35 - Install Laravel 11
1:25 - Sqlite as the default database driver
1:58 - Comparing Laravel 10 and Laravel 11
2:20 - The new Laravel 11 app directory
3:30 - Laravel 11 config directory
3:47 - Publishing your Laravel 11 config
4:34 - Laravel 11 migration changes
5:24 - Laravel 11 routes files
5:40 - How to bring back API routes
6:20 - Laravel 11 console kernel
6:49 - New Laravel 11 Model casts are a method
7:30 - Conclusion
➫ Business Inquires: hello@laravel-news.com
----------------------------------------------------------------------
JOIN OUR WEEKLY LARAVEL NEWSLETTER
laravel-news.com/newsletter
----------------------------------------------------------------------
#laravel11 #laravelphp #laraveltutorial

Наука

Опубликовано:

13 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 53

@laravelnews 5 месяцев назад

Written tutorial on this here: laravel-news.com/laravel-11-directory-structure

@cabanelas 5 месяцев назад

Too many essential stuff gone or hidden... confusing.

@guramikutivadze 5 месяцев назад

It looks like someone just went to my room, moved the staff into the closet, and now I have to get everything back.

@jeffreysmith9837 5 месяцев назад

Exactly. It's fucking stupid lol what is the point of this dumb shit

@gkrondon 5 месяцев назад

To say that most people don't use Laravel API routes look a little strange for me, at least considering my experience... But since it's still possible to easily implement those and Laravel documentation is usually well done and explained with lots of use cases, seems like a nice simplification for those who are starting with the framework and doesn't need all those features from the beginning

@laravelnews 5 месяцев назад

Yeah, good point. I was just going from my own experience and most times I'm not creating an api. The joys of different types of projects we all build.

@ciberman 5 месяцев назад

I am worried that newbies will not know about all the features that Laravel has built in and reinvent the wheel. I've seen it with Laravel < 10 projects. So it will be a lot more common now that a lot of things are hidden.

@binaryfire 4 месяца назад

What happens if you need to fully customize / override middleware groups? I've only seen prepend and append methods in the new bootstrap.php. I have tenancy middleware that needs to go in the middle of the default web and api stacks.

@amkashif171 4 месяца назад

Just before the release of the Laravel 11, Taylor Otwell just decided to give back some basic necessary config files in config directory so these are now available

@laravelnews 4 месяца назад

Yep indeed! The still can cascade though so technically you can remove them if wanted but they are back to being included.

@devopsdevelopoptions409 5 месяцев назад

it also make some changes to the migration other that keeping then in order they make the session table by default created and also summed all of the tables related to the users as an example in one migration and also they added a new migration for cache and this is not found in laravel 10

@mr.codehappy 5 месяцев назад

pls, you use theme extension of visual studio code ?

@MadalinIgnisca 5 месяцев назад

I was so hopping to have 'app' => 'src', or at list framework's code fixed so it won't break when you change it.

@tarreislam 4 месяца назад

Yeah this to

@krakatoom 4 месяца назад

I just got laravel 11 working with sail just to notice that using sail the folder structure is still the same as in 10...

@fafaratze 5 месяцев назад

so you can just extend configuration files?

@binaryfire 5 месяцев назад

Will any config files you add be merged with the default configs of the same name? Eg. let's say you created 'config/database.php' and only defined the redis array - would that work?

@devhammed 5 месяцев назад

Yes, it will be merged with the framework defaults so you can provide only what you want to customize.

@binaryfire 5 месяцев назад

@@devhammed Thanks!

@nevmerzhitsky 5 месяцев назад

@@binaryfire It's not cleaner at all when you just want to know a default value of an option, but you still don't need to publish/override this option. I mean how should I locate the default values of the standard options of the framework in my IDE. It's getting difficult.

@kwyaza 5 месяцев назад

Very cool. I like the clean structure. One weird thing is to have the console cron schedules under routes. It would probably be better to have the api routes and console in the App/Console folder.

@jaspercaelan4998 3 месяца назад

Laravel 11: we've spent a year deleting stuff so you can spend more time looking up console commands to bring it back when you install Laravel. This is the definition of busywork.

@laravelnews 3 месяца назад

Nah. This is all for new people coming into php and laravel. If you are already using it and comfortable then you can keep everything the same as you have it now.

@evercode1863 5 месяцев назад

I can't think of single actual benefit to the streamlined structure. For those of us that use config, mysql, kernel, middleware, console commands, api routes, we now have to go through the cost of rearranging our applications to what benefit? 0. Having a dedicated folder for middleware makes a lot of sense. One of the great things about Laravel is how intuitive everything is. Laravel 11 is working against that. To restructure our applications for Laravel 11, big pain, little to 0 benefit. Still wondering if I should do it.

@laravelnews 5 месяцев назад

This is for new apps only. Your existing structure will keep working.

@jeffreysmith9837 5 месяцев назад

Don't bother. And they will break it again in v12 in 6 months

@tarreislam 4 месяца назад

@@jeffreysmith9837 wdym? Many poeple does not even use the default laravel structure to begin with. You could technically run an entire Laravel application with everything in the same folder and have it run like that forever

@bugszone6098 4 месяца назад

font ar too small, you should care about it

@EnriqueMunoz-no1fq 5 месяцев назад

Personally i dont like the idea that much, i like to hace configuration and structure of the app at hand, so i can see what options i have and better decide. I feel like that is something i like much about Laravel so far. That i can see the configuration of my app at first sight. I mean, Laravel is not a minimal framework, it it a batteries included one, i like to see all the bateries at my disposal hahaha. I would propose that at least there should be an artisan command to bring back all the configuration files and options to where they are now as of Laravel 10. Maybe its just me but man, this is not a js framework :(

@laravelnews 5 месяцев назад

That's possible. If you want to publish any given configuration file from the framework to customize it, you can use the config:publish command: # config/database.php php artisan config:publish database # config/logging.php php artisan config:publish logging # Or publish all of them php artisan config:publish

@EnriqueMunoz-no1fq 5 месяцев назад

@@laravelnews Yeah, i get that part, that is only config folder tho, i meant one command to come back to Laravel 10 Folder structure practically

@JamesAutoDude 5 месяцев назад

@@EnriqueMunoz-no1fqsadly that wouldn't happen since the update is meant to change that... If they had that option then it wouldn't be a change lol

@giorgi316 4 месяца назад

When i install laravel from docs why config files still exists?

@giorgi316 4 месяца назад

i mean files inside config

@chamalayesh1533 5 месяцев назад

Interesting...

@ellmatic 4 месяца назад

Interesting...

@359WiseGuy 4 месяца назад

If something works for a long time, DON'T TOUCH IT AND DON'T CHANGE IT :D

@kreatur_ 5 месяцев назад

I'm still having mixed feelings about this change

@zunnur1 5 месяцев назад

I totally love this.

@rainfizz 3 месяца назад

this make upgrading process complex😩

@LotusSoftPvtLtd 4 месяца назад

the volume of your voice is small in your video.

@tarreislam 4 месяца назад

Tbh more stuff could be removed and created when needed.

@regisk7 3 месяца назад

What is happening is that, Laravel Team realized they were giving away too much thing for free and now they are cutting back, hiding things and making everything difficult to find. This the road to make more core stuff behind paywall.

@laravelnews 3 месяца назад

No, that isn't accurate at all.

@regisk7 3 месяца назад

@@laravelnews Not yet, you will see in time.

@albertolago1011 4 месяца назад

Who are you? What's your name? you don't have to leave a C.V. but only introduce yourself as a way to get you trusted in other videos... Ah! this is a video from "Mike". Sure it is good (no matter what it is about ...)

@laravelnews 3 месяца назад

Hi I’m Eric creator of Laravel News. Why does it matter though? Either you enjoy the video or not. 😅

@jeffreysmith9837 3 месяца назад

Fuckin weirdo

@CoolioBeans 2 месяца назад

3:40 "Boom, no files" This is honestly the most useless overview of the "streamlined" directory structure. There is no explanation about why these directories were removed or detailed explanation on the implications of these changes. Disappointing overview.

@jeffreysmith9837 5 месяцев назад

This is stupid lol. I fucking hate software sometimes

@Shiv-vb1re 5 месяцев назад

It makes sense because not everyone use all parts of laravel and thus don't require dependencies this will reduce the size and increase performance of the app

@jeffreysmith9837 5 месяцев назад

@@Shiv-vb1re this does nothing for performance. The code is still there it's just hidden in /vendor