While seeding data, it’s common to have one class for each database table. But what if there are relationships? I
This post is inspired by some discussions that appear constantly in various forums or social media channels. Question of the day/month/year: why is there no app/Models folder? And do we need one?
While working internally with Laravel APIs and Vue.js, decided to create a sample open-source project to show how it all works together.
In some systems it is required to change password every X days: in banking sector, or working with more sensitive data. Laravel doesn’t have that functionality out-of-the-box, but it’s easy to build. Let’s do it today.
Let’s imagine a scenario where you have an old database and re-writing codebase to Laravel. Database structure may not follow Laravel standards – created_at and updated_at fields are named differently. How can you “tell it to Laravel”?
Not Laravel related, but today encountered the situation, so sharing with you. You probably know Datatables, right? It allows to quickly search and filter the table of data. But what if user then navigates away (for Edit, for example) and then wants to go back and have the same search parameters he had before? Easy.
Laravel is a back-end framework, but most web-projects still require a front-end theme. And there are no sites with “Laravel themes”, all front-end themes are mostly based on WordPress CMS. But it shouldn’t be a problem – we can easily transform a WP theme to Laravel Blade. We often do that for our clients, so I will show you a simple example.
Laracasts is the no.1 place to learn Laravel, no doubt. But if you don’t want to pay for subscription or just like to use YouTube, there are people who can teach you there. I’ve searched through YouTube and picked the best ones, in my opinion.