This episode is for members only
Sign up to access "Build An Uptime Monitor with Inertia" right now.
Get started
Already a member? Sign in to continue
Playing
22. Making an HTTP request
Episodes
01. Introduction
02. Sites
03. Endpoints
09. Setting up endpoints
4m 23s
0%
10. Enum endpoint frequencies
3m 50s
0%
11. Creating the endpoint form
12m 58s
0%
12. Storing an endpoint
7m 21s
0%
13. Validating and authorizing endpoint stores
7m 6s
0%
14. Normalizing the endpoint location
6m 4s
0%
15. Displaying endpoints
6m 22s
0%
16. Deleting endpoints
6m 21s
0%
17. Toggling inline editing for endpoints
5m 12s
0%
18. Applying a watcher to the endpoint form
5m 31s
0%
19. Storing endpoint edits
8m 56s
0%
04. Checking endpoints
20. Determining endpoints to check
2m 57s
0%
21. Creating a job to perform a check
3m 21s
0%
22. Making an HTTP request
3m 39s
0%
23. Scheduling checks every second
4m 27s
0%
24. Setting up the check relationship
3m 14s
0%
25. Updating the job
2m 10s
0%
26. Showing the last status
12m 50s
0%
27. Expanded list of checks
14m 10s
0%
28. The response body modal
2m 49s
0%
29. Authorizing the endpoint details
2m 27s
0%
30. Calculating uptime for endpoints
8m 29s
0%
06. Email notifications
07. Downtime notifications
Transcript
00:00
Laravel has an HTTP client wrapper around Guzzle, which allows us to very, very easily make requests. And as you'd imagine with Laravel,
00:08
it's also very nice to use. So we're going to go ahead and use this. And this is actually going to be incredibly simple, because all we're really doing here
00:17
is making a GET request to these particular endpoints. Of course, later on, if you wanted to add the ability to make a POST or PATCH request through, you could add columns in here to specify the type.
00:30
We may get to that a little bit later. But for now, we just want to make a GET request to the location here. And of course, making sure we add on the domain name
00:39
that we're sending the request to as well. So let's get started. And we're not going to store our checks anywhere just yet, because we don't have a table for that at the moment.
00:46
But we'll just dump some of the data out just to see what we get. So the first thing I'm going to do really importantly is add this around to TRICATCH.
00:54
So we're going to go ahead and catch any general exception here. And we're actually going to do nothing, because when we make the request here
01:02
and we get the response back from the HTTP client, this is going to tell us whether the request was successful. We just want to catch any exception here just in case something does go wrong and we don't want
01:13
to completely break the job. So to use the HTTP client, we just use the facade here. And of course, we're just making a GET request. So we're just going to use the GET method.
01:24
And then we want to grab the full URL from the endpoint. Now, at the moment, we don't have this in here. We have the site, so we could access that relationship and add that on.
01:34
But why don't we just do this in a method? It's probably going to make it a little bit easier. So let's go ahead and create our URL method on our endpoint. And we're going to go ahead and reference the site URL, which
01:47
we implemented a little bit earlier. We just have a look here. That's this one here. And then we're going to go ahead and concatenate on the location.
01:57
So now this URL should give us, if we head over here, the entire URL that we want to make a request to. So we can now just say endpoint URL. Now, that is pretty much all we're
02:08
doing to make a request to the endpoint. The beauty in this is the data that we actually get back from this. So let's just go ahead and dump out some of the data
02:19
that we get back from the response. So we're going to go ahead and say response status, first of all. Let's try that one first. Now, at the moment, I'm not sure when these next checks are.
02:28
But let's go ahead and just run the command anyway and just see what we get. There we go. We get a 404.
02:34
Now, that is probably for slash pricing, because that doesn't exist over on CodeCourse. Let's just change this over to pro and this one over to forward slash, which both do exist.
02:45
And let's set the next check time to now, just so we can speed this along. Let's add both of these now. Obviously, we won't get to this one, because we're
02:54
dying and dumping here. Let's go ahead and do that. And sure enough, we get a 200. So this is working nicely.
02:59
And we're getting back the data we want to be able to determine whether it was successful. Now, we also have things like a successful method. So if we just go ahead and run this, we get true, of course.
03:10
And we also have things like body, as well, which is going to give us back the response we get from this request, which, as we know from the introduction, we're going to store when we get an unsuccessful request.
03:20
So as long as we have a successful request, we're not going to store the body. But if it's unsuccessful, we are going to store this body. So that is pretty much it for the HTTP request.
03:31
We may have originally thought it would be a lot more difficult than this. But of course, with Laravel, everything is nicely wrapped and really, really simple to use.
44 episodes•4 hrs 59 mins•1 year ago
Overview
Ready to dive into Inertia? Let's build a real-world app with Laravel, Inertia and Vue! If you're already working with Inertia, you'll pick up some tips and techniques for future projects.
This uptime monitor allows you to create and switch between sites, then add endpoints to monitor with frequency intervals. Using the power of scheduling and queues, it'll automatically alert the email addresses you've added via the UI when an endpoint goes down.
In this course, you'll learn to:
- Build a real app from scratch with Inertia
- Work with Laravel queues
- Perform actions on models at user-defined intervals
- Work with sub-minute schedules in Laravel
- Send out channel notifications with Laravel
- Use API resources to simplify Inertia data
- Organise apps with events and observers
- Create modals in Vue
- Perform inline editing with Inertia forms
Alex Garrett-Smith
Hey, I'm the founder of Codecourse!
Comments
No comments, yet. Be the first to leave a comment.