Sign up to access "Build an E-Commerce Platform" right now.

We're going to do a very plain email in this episode and then we can fill this in a little bit later on. First of all, though, we want to go ahead and actually get set up with local email. For this, I'm going to use MailHug. It doesn't matter what you use, whether you use a piece of software like Hello or use a third party service like MailTrap, really doesn't matter.

But if you're interested in setting MailHug up, this is how we do it. Now, I'm running on a Mac, so I just use brew update and brew install MailHug. But there are other options depending on your operating system. Now, once you've done that, you'll be able to access this over on port 8025 on local.

Once you've started the MailHug server. So I already have this installed. I'm just going to go ahead and run this over in my terminal. And that's going to boot up a server which we can now access. And all of your emails that you send through Laravel should now roll into this fake inbox.

Now, we might need to configure this. So if we just head over to EMV, head over to our mail section, you can see Laravel is actually pretty much already set up to use MailHug here. The username and password can be null. Same with encryption.

The only thing we do need to add is the mail from address. I'm just going to set that to Alex at CodeCourse.com. OK, so let's go ahead and send out an email in here. The first thing that we need to do is actually generate out an email

and we'll call this order status updated. OK, so that's created out a mailable order status updated. If you want to, rather than return a view here, you could go ahead and put this as a markdown email.

Just to show you that really quickly, if you're new, let's get rid of this order status updated. What you can do is do pretty much the same thing, but provide the markdown option and then in here give the path to the markdown. For example, emails orders updated.

So if we just go ahead and check this out, order status updated, this will now point to a markdown file. And if we open updated.blade.php, this basically allows you to define this in markdown within Laravel.

Let's leave it like this because it's a little bit nicer. So in here your order has been updated or the status of your order has changed and we could grab this and go ahead and set that as a subject of the email. So let's do that and then we'll fill the rest of the information out in here later.

OK, let's actually send the email. So over in our order observer, this is where we want to do this. Now, we're not going to queue this just yet. Let's go ahead and say order to and who are we sending this to?

Well, on the order we have a user relationship. That is who we're sending it to. Let's make sure we put in the mail facade and we want to send a new order status updated email

and into this we probably want to pass the order. So that's the original order here that has been changed. So we're going to have all of that updated information. So in order status updated, let's go ahead and accept this in as a dependency.

So let's say public order order and make sure we pull the namespace in. So that will now be available in the template so we can grab any of the information about that. For example, we could go ahead and say hash and then order ID.

We'll leave it at that for now. Okay, let's go ahead and check that this actually sends the email. So first of all, let's head over to the database, switch packaged at and shipped at to null

and let's go back over from phps and tinker. Let's go ahead and grab that order out. So order find one and let's say order update and packaged at and set that to now.

Okay, it looks like we've got an error here that she's sending the email. Let's just revert packaged at back for now. I think that's just because over in EMV, we're going to go ahead and set the mail host to local host rather than mail hog.

That's just if you're using Laravel sale, which we're not in this case. And let's go ahead and try this again. So we're going to go ahead and say order update packaged at now

and make sure we quit out of tinker first so the settings come in. So let's find that order and go ahead and switch that over and we should be good. Great. So let's go over to mail hog.

There we go. We get a email here, of course sent to the user who has placed the order and the status of your order hash one has changed and you could technically go ahead and grab the status out in here,

maybe link through to the orders page, whatever you needed to do. So we'll leave it at that for now because sending the email is the most important part.

You can go ahead and fill in either the markdown in here or if you wanted to generate out a plain view, you could do that as well, but we'll come back to this later and fill it in just to tidy things up.