How to Seed More Data When Laravel Project is Live
If you have 10 rows of data in the initial Seeder file, but then you need to import 10 more rows when the project is already launched, what should you do? There are a few options.
In-depth Laravel tutorials covering advanced topics, real-world examples, and best practices.
If you have 10 rows of data in the initial Seeder file, but then you need to import 10 more rows when the project is already launched, what should you do? There are a few options.
Let's say you have a Login page with the language prefix in URL: `/en/login` and `/fr/login`. To show French/English texts on the Login page, you need to do these things.
There are situations when we're not sure what the columns of the DB table would be, they need to be flexible. For example, e-shop product properties: size, color, fabric, there may be more in the future. What is the best DB structure? I will show you 3 options and their performance.
Sometimes you need to add more fields to the many-to-many pivot table, and those fields may also have their own relationships.
In default Laravel, there's one constant responsible for the redirection of logged-in users. How is it used in Breeze?
To deploy assets with Vite to the live server, one of the ways is to build them locally and then push the built assets to the repository.
The default naming convention of Laravel many-to-many pivot table is xxxxx_yyyyy, where "xxxxx" and "yyyyy" are names of related tables, in singular form, in alphabetical order.
In Laravel's many-to-many polymorphic relations, there is a situation where you can't get ALL records of different models by their "parent" record. Let me explain, and show the potential solution.
When using a relationship, have you ever seen an error like "Attempt to read property on null"? It usually means that the related record is NULL or soft-deleted. There are multiple ways to gracefully handle such a situation, without showing the error to the user.
What if your customer is filling in the order form, and meanwhile the product price has changed? Or, some product becomes out of stock? We need to re-validate the quantities/prices after the submit, right? In this article, I will show you two ways: regular Laravel and more UX-friendly "live validation" with Livewire.