In-depth Laravel tutorials covering advanced topics, real-world examples, and best practices.
In this chapter of my e-book let’s take on the "holy war" between frameworks. I’m not kidding here - developers actually fight (verbally only, I hope) with each other about what framework to use.
There is a new interesting project on the market - a map of developers. Started as a Laramap by Florian Wartner, now it became a broader project, presenting to you PHPMap.co!
Yes, you've read it right - thoughts and feelings, not review or recap. This article will be filled with emotions, cause that was my first Laracon and for me it was a lot of new thing, meeting people etc.
(Guest post by Oliver Hermanni) Some days ago Povilas wrote a post why it's bad to code PHP on Windows. He got quite a lot of comments there and on Twitter - and to be honest, not all of them where nice. Unfortunately this is a regular problem - Apple users tend to overreact when it's about Windows. I'm not sure, if most of them ever worked with Windows or why it's still cool to hate it.
The name PyroCMS is not new on the market - it was actually created as a CodeIgniter-based system and became quite popular. And recently the shift was made - the whole system was re-created into Laravel framework. So what do we have with a new PyroCMS 3?
New video on my Youtube channel Laravel Business - today I want to talk about what to talk about (ironical, right) with the client before the beginning of the project. Usually those conversations save huuuuge amount of time (and potential failures) in process of the project.
Today I've delivered a presentation at my local Laravel Meetup in Vilnius, Lithuania, and now sharing slides with you. Basically, I wanted to research what are available solutions on the market to generate Laravel code automatically instead of writing it manually. Found quite a lot, actually. So now have a bigger picture on various generators and some new ideas for our own QuickAdminPanel generator.
When creating user authorization system with soft-deletable data we might encounter a problem: deleted user might try to register with same email address and gets an error that it is in use. What to do in order to prevent it? Here is a quite simple example of how it could be solved.
Laravel default Auth system is great, but sometimes there's a need that user would register but NOT log in automatically. The problem is that Laravel does auto-login by default after registration. Worry no more, there is a simple solution for that!
Another side-project from my team and me personally. Lately there's quite a lot of books about Laravel, as the framework gets more popular. But the thing I've missed on the market is a non-technical book about Laravel. So here it is - presenting to you "Laravel for Clients"!
