For those who finds difficulty creating stack.json , here you can find in my repo https://github.com/khizarSulehria/laracast-laravel-servers/blob/master/stack.json

May I have stack.json file?

Would be very cool to get the stack.json

You should have explained where that id for the image with ubuntu came from...

Now I could copy the id from your video, but still dont know where to find these.

@hotgeart Good luck with your many problems coding and in life.

@SosoRicsi that would be more like parents-children but I see your point

Whoop Whoop! I was just watching the previous episode when I got an email that the series was updated.

Thanks Jeffrey for creating awesome content ;)

Hey Joe,

first, thanks for this series.

I was watching this episode and I see you make use of Channel->isSubscribed(). I re-watched all videos to see where that came from and couldn't find anything. I checked the repo and there I see that you have a Models/Channel and Models/Message classes. These classes are never introduced. Not even in the installation video. I believe it is confusing as we can't actually understand how a user can be subscribed if we don't know that there is a table for it in the database.

Maybe you should have another video explaining the base of the application as these 2 classes (and their methods) are pivotal to understanding how the messaging system works.

Keep it up!

If you're not receiving events when sending data through WebSocket, a solution that worked for me is running the command php artisan queue:listen. This resolved the issue for me and allowed events to be received. Give it a try if you're experiencing the same problem!

@alessandro.mirabelli I can't promise anything, but we'll see. I recorded this episode several times, and that was my reaction to finally getting a take I could use. I originally intended to cut it out.

I’ve seen all the episodes, but this one was exceptional 💪

@JeffreyWay You set the expectations too high for the rest of us, fixing bugs that fast! Thanks Jeffrey

@mrrobotoh I have submitted a support ticket as it seems the issue is still here.

@mrrobotoh Sorry about this! All fixed now.

I can’t find the repo. Am I blind?

the link https://laravelfromscratch.com seems to be broken

It looks like the video cuts off too early (length of video is around 2mins). But the episode summary does show the completion of extraction of the modal.

@teutonius It's one of those little gotchas that can result in a huge problem. glad this helped.

@chilldsgn this is a great follow-up to that series!

@krekas Thanks! We've fixed the run-time.

content => 'poly relationships are cool'
That could be taken in a couple different ways

My sides 🤣

@sean2025 I'm so glad this series was helpful to you. Thanks for leaving this review!

Great serie on TALL stack!

Thank you for this series! I've never used livewire at all before this but i will use it in future projects now!

Heads up that in Episode 8, we'll continue reviewing getters and setters, and specifically how we can prepare them in PHP 8.4, which introduced support for property hooks.

Nice. Describing this fundamental yet abstract PHP interface concept in the simplest terms as a feature filter while introducing Laravel's (rather) consistent terminology of "Contract" helped me better understand implementation vs interface principles. Appreciate the bare bones descriptions in this OOP series. Thanks.

the best series of PHP in the history thank you jeffrey

Why the parenthesis around the call to new Auth and new Guest ?

@pelachile The parenthesis are there so the handle() method can be called on the instantiated class directly, without having to assign the instance to a variable. Little cleaner and little better for performance since you don't assign to variable.

Best instructor ever 🫡

@chang180 Why would you want to handle something like that?

If a user maliciously tries to modify a locked property, he will see a 500 Internal Server Error without the helpful message that we see at local because of the APP_DEBUG setting in .env.

I personally wouldn't worry about a message to that particular type of user, because he knows very well what he is doing.

@facmartoni Thanks for the clarification! I didn’t realize that in a production environment, it would respond with a 500 Internal Server Error. That makes a lot more sense now. Appreciate your input!

@chang180 You're welcome! Great that I helped :)

Please note that this new series will be the official replacement for "The PHP Practitioner," which we released in 2016. http://laracasts.com/series/php-for-beginners

Here's the source code this course!

https://github.com/laracasts/laravel-workshop

@fireball70 Don't fool yourself into believing the latest thing is the correct thing.

Ziggy works beautifully in this case...ESPECIALLY as we're migrating from dozens and dozens of Blade file route() references.

HeadlessUI is maintained and managed by the Tailwind CSS team - the biggest CSS framework in the world.