Back Button Laravel
Laravel 6 From Scratch

Laravel 6 From Scratch

In this series, step by step, I'll show you how to build web applications with Laravel 6. We'll start with the basics and incrementally dig deeper and deeper, as we review real-life examples. Once complete, you should have all the tools you need. Let's get to work!

51 episodes
5:45:09 hrs
Latest Episode in This Series

Added 16 hours ago

Authorization Filters

There will almost certainly be users in your application who should receive special privileges and access. As...

Laravel 6 From Scratch

Laravel 6 From Scratch

In this series, step by step, I'll show you how to build web applications with Laravel 6. We'll start with the basics and incrementally dig deeper and deeper, as we review real-life examples. Once complete, you should have all the tools you need. Let's get to work!

Latest Episode in This Series

Added 16 hours ago

Authorization Filters

There will almost certainly be users in your application who should receive special privileges and access. As...


Your Teacher | Jeffrey Way's avatar
Hi, I'm Jeffrey. I'm the creator of Laracasts and spend most of my days building the site and thinking of new ways to teach confusing concepts. I live in Orlando, Florida with my wife and two kids.
  1. Section 1 Prerequisites

    1. EPISODE 1

      Run Time 2:40


      Before we dig into the nuts and bolts of Laravel, let's first zoom out and discuss what exactly happens when a request comes in.

    2. EPISODE 2

      Run Time 3:33


      Before we get started, you must first ensure that up-to-date versions of both PHP and MySQL are installed and available on your machine. In this episode, we'll review how to go about this. Once complete, we can then install Composer.

    3. EPISODE 3

      Run Time 3:02


      Now that we have Composer setup, we can pull in the Laravel installer and make it accessible globally on our machine. This allows you to run a single command to build a fresh Laravel installation: laravel new app.

    4. EPISODE 4

      Run Time 3:18


      If you're a Mac user, rather than running php artisan serve, you might instead choose to install Laravel Valet. Valet is a blazing fast development environment for Laravel that's a cinch to setup.

  2. Section 2 Routing

    1. EPISODE 5

      Run Time 3:41


      When I learn a new framework, the first thing I do is figure out how the framework's default splash page is loaded. Let's work through it together. Our first stop is routes/web.php.

    2. EPISODE 6

      Run Time 4:11


      The request() helper function can be used to fetch data from any GET or POST request. In this episode, we'll learn how to fetch data from the query-string, pass it to a view, and then encode it to protected against potential XSS attacks.

    3. EPISODE 7

      Run Time 3:42


      Often, you'll need to construct a route that accepts a wildcard value. For example, when viewing a specific post, part of the URI will need to be unique. In these cases, we can reach for a route wildcard.

    4. EPISODE 8

      Run Time 3:01


      It's neat that we can provide a closure to handle any route's logic, however, you might find that for more sizable projects, you'll almost always reach for a dedicated controller instead. Let's learn how in this lesson.

  3. Section 3 Database Access

    1. EPISODE 9

      Run Time 6:13


      So far, we've been using a simple array as our data store. This isn't very realistic, so let's learn how to set up a database connection. In this episode, we'll discuss environment variables, configuration files, and the query builder.

    2. EPISODE 10

      Run Time 3:45


      In the previous episode, we used the query builder to fetch the relevant post from the database. However, there's a second option we should consider: Eloquent. Not only does an Eloquent class provide the same clean API for querying your database, but it's also the perfect place to store any appropriate business logic.

    3. EPISODE 11

      Run Time 5:23


      In a previous episode, we manually created a database table; however, this doesn't reflect the typical workflow you'll follow in your day-to-day coding. Instead, you'll more typically reach for migration classes. In this episode, we'll discuss what they are and why they're useful.

    4. EPISODE 12

      Run Time 1:26


      It can quickly become tedious to generate all the various files you need. "Let's make a model, and now a migration, and now a controller." Instead, we can generate everything we need in a single command. I'll show you how in this episode.

    5. EPISODE 13

      Run Time 7:36


      When possible, the code you write should reflect the manner in which you speak about the product in real life. For example, if you run a school and need a way for students to complete assignments, let's work those terms into the code. Perhaps you should have an Assignment model that includes a complete() method.

  4. Section 4 Views

    1. EPISODE 14

      Run Time 4:11


      If you review the welcome view that ships with Laravel, it contains the full HTML structure all the way up to the doctype. This is fine for a demo page, but in real life, you'll instead reach for layout files.

    2. EPISODE 15

      Run Time 4:27


      Using the techniques you've learned in the last several episodes, let's integrate a free site template into our Laravel project, called SimpleWork.

    3. EPISODE 16

      Run Time 2:15


      In this episode, you'll learn how to detect and highlight the current page in your navigation bar. We can use the Request facade for this.

    4. Laravel provides a useful tool called Mix - a wrapper around webpack - to assist with asset bundling and compilation. In this episode, I'll show you the basic workflow you'll follow when working on your frontend.

    5. EPISODE 18

      Run Time 6:19


      Let's next learn how to render dynamic data. The "about" page of the site template we're using contains a list of articles. Let's create a model for these, store some records in the database, and then render them dynamically on the page.

    6. EPISODE 19

      Run Time 5:05


      Let's finish up this exercise by creating a dedicated page for viewing a full article.

    7. EPISODE 20

      Run Time 2:45


      Let's review the solution to the homework from the end of the previous episode. To display a list of articles, you'll need to create a matching route, a corresponding controller action, and the view to iterate over the articles and render them on the page.

  5. Section 5 Forms

    1. EPISODE 21

      Run Time 5:03


      There are seven restful controller actions that you should become familiar with. In this episode, we'll review their names and when you would reach for them.

    2. EPISODE 22

      Run Time 7:37


      Now that you're familiar with resourceful controllers, let's switch back to the routing layer and review a RESTful approach for constructing URIs and communicating intent.

    3. EPISODE 23

      Run Time 7:55


      Now that you understand resourceful controllers and HTTP verbs, let's build a form to persist a new article.

    4. EPISODE 24

      Run Time 6:35


      Browsers, at the time of this writing, only recognize GET and POST request types. No problem, though; we can get around this limitation by passing a hidden input along with our request that signals to Laravel which HTTP verb we actually want. Let's review the basic workflow in this episode.

    5. EPISODE 25

      Run Time 8:53


      Before we move on to cleaning up the controller, let's first take a moment to review form validation. At the moment, our controller doesn't care what the user types into each input. We assign each provided value to a property and attempt to throw it in the database. You should never do this. Remember: when dealing with user-provided data, assume that they're being malicious.

  6. Section 6 Controller Techniques

    1. EPISODE 26

      Run Time 4:56


      So far. we've been manually fetching a record from the database using a wildcard from the URI. However, Laravel can perform this query for us automatically, thanks to route model binding.

    2. EPISODE 27

      Run Time 5:40


      Your next technique is to reduce duplication. If you review our currentArticlesController, we reference request keys in multiple places. Now as it turns out, there's a useful way to reduce this repetition considerably.

    3. EPISODE 28

      Run Time 3:58


      Named routes allow you to translate a URI into a variable. This way, if a route changes at some point down the road, all of your links will automatically update, due to the fact that they're referencing the named version of the route rather than the hardcoded path.

  7. Section 7 Eloquent

    1. EPISODE 29

      Run Time 6:07


      Let's now switch back to Eloquent and begin discussing relationships. For example, if I have a $user instance, how might I fetch all projects that were created by that user? Or if I instead have a $project instance, how would I fetch the user who manages that project?

      For a deeper dive, please review the Eloquent Relationships Laracasts series.

    2. Let's put our learning from the previous episode to the test. If an article is associated with a user, then we need to add the necessary foreign key and relationship methods. As part of this, though, we'll also quickly review database factories and how useful they can be during the development and testing phase.

    3. Next up, we have the slightly more confusing "many to many" relationship type. To illustrate this, we'll use the common example of articles and tags. As we'll quickly realize, a third table is necessary in order to associate one article with many tags, and one tag with many articles.

    4. EPISODE 32

      Run Time 5:04


      Now that we've learned how to construct many-to-many relationships, we can finally display all tags for each article on the page. Additionally, we can now filter all articles by tag.

    5. EPISODE 33

      Run Time 12:17


      We now understand how to fetch and display records from a linking table. Let's next learn how to perform inserts. We can leverage the attach() and detach() methods to insert one or many records at once. However, we should also perform the necessary validation to ensure that a malicious user doesn't sneak an invalid id.

  8. Section 8 Authentication

    1. EPISODE 34

      Run Time 9:26


      Thanks to the first-party package, Laravel UI, you can easily scaffold a full registration system that includes sign ups, session handling, password resets, email confirmations, and more. And the best part is you can knock out this tedious and common minutes.

    2. EPISODE 35

      Run Time 8:40


      In this episode, we'll discuss the basic password reset flow. If a user forgets their password, a series of actions need to take place: they request a reset; we prepare a unique token and associate it with their account; we fire off an email to the user that contains a link back to our site; once clicked, we validate the token in the link against what is stored in the database; we allow the user to set a new password. Luckily, Laravel can handle this entire workflow for us automatically.

  9. Section 9 Core Concepts

    1. EPISODE 36

      Run Time 11:21


      Our first core concept is collection chaining. As you've surely learned by now, when fetching multiple records from a database, a Collection instance is returned. Not only does this object serve as a wrapper around your result set, but it also provides dozens upon dozens of useful manipulation methods that you'll reach for in every project you build.

    2. EPISODE 37

      Run Time 9:13


      Laravel provides Cross-Site Request Forgery (CSRF) protection out of the box, but you still may not know exactly what that means. In this lesson, I'll show you a few examples of how a CSRF attack is executed, as well as how Laravel protects your application against them.

    3. EPISODE 38

      Run Time 5:15


      Laravel's service container is one of the core pillars of the entire framework. Before we review the real implementation, let's first take a few moments to build a simple service container from scratch. This will give you an instant understanding of what happens under the hood when you bind and resolve keys.

    4. EPISODE 39

      Run Time 11:04


      Now that you understand the basics of a service container, let's switch over to Laravel's implementation. As you'll see, in addition to the basics, it can also, in some cases, automatically construct objects for you. This means you can "ask" for what you need, and Laravel will do its best - using PHP's reflection API - to read the dependency graph and construct what you need!

    5. EPISODE 40

      Run Time 13:55


      Now that you have a basic understanding of the service container, we can finally move on to Laravel facades, which provide a convenient static interface to all of the framework's underlying components. In this lesson, we'll review the basic structure, how to track down the underlying class, and when you might choose not to use them.

    6. EPISODE 41

      Run Time 11:18


      We've spent the last two episodes reviewing Laravel's service container and facades. All of that work is about to pay off, as we move on to service providers. A service provider is a location to register bindings into the container and to configure your application in general.

  10. Section 10 Mail

    1. EPISODE 42

      Run Time 6:50


      The easiest way to send an email in Laravel is with the Mail::raw() method. In this lesson, we'll learn how to submit a form, read a provided email address from the request, and then fire off an email to the person.

    2. EPISODE 43

      Run Time 1:07


      It's useful to view a log of any mail that is sent while in development mode, but let's switch over to using Mailtrap. This will allow us to simulate a real-life email inbox, which will be especially useful once we begin sending HTML email.

    3. EPISODE 44

      Run Time 4:40


      So far, we've only managed to send a basic plain-text email. Let's upgrade to a full HTML-driven email by leveraging Laravel's mailable classes.

    4. EPISODE 45

      Run Time 8:52


      We can alternatively write emails using Markdown! In this lesson, you'll learn how to send nicely formatted emails constructed by the framework. For the cases when you need to tweak the underlying HTML structure, we'll also publish the mailable assets and review how to create custom themes.

    5. EPISODE 46

      Run Time 8:02


      So far in this chapter, we've exclusively reached for Mailable classes to send emails; however, there's an alternative approach that you might consider as well. A Notification class can be used to notify a user in response to some action they took on your website. The difference is in how the user is notified. Sure, we can send them an email, but we could also notify them via a text message, or Slack notification, or even as a physical post card!

  11. Section 11 Notifications

    1. EPISODE 47

      Run Time 13:21


      A notification may be dispatched through any number of "channels." Perhaps a particular notification should alert the user via email and through the website. Sure, no problem! Let's learn how in this episode.

    2. EPISODE 48

      Run Time 5:40


      Here's a fun exercise. For this next notification channel, we'll choose one that I've personally never used: SMS messaging. As you'll see, even with no prior experience, it's still laughably simple to conditionally fire off text messages to the users of your application.

  12. Section 12 Events

    1. EPISODE 49

      Run Time 14:35


      Events offer a way for one part of your application to make an announcement that ripples through the entire system. In this episode, we'll not only review the essentials, but we'll also discuss the pros and cons to this particular approach to structuring an application.

  13. Section 13 Authorization

    1. EPISODE 50

      Run Time 19:51


      For any typical web application, some actions should be limited to authorized users. Perhaps only the creator of a conversation may select which reply best answered their question. If this is the case, we'll need to write the necessary authorization logic. I'll show you how in this lesson!

    2. EPISODE 51

      Run Time 3:55


      There will almost certainly be users in your application who should receive special privileges and access. As examples, consider a forum moderator or site administrator. In these cases, we can declare before and after authorizations filters before the intended policy ability is tested.

Series still in development robot

*Series still in development. Check back often for updates.