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
24. Setting up the check relationship
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
For every check that we perform on an endpoint we of course want to go ahead and store this. So let's start by creating out a model for each of our checks, of course with a migration alongside of that. So let's head over to the create checks table migration and let's think about some of the data that we need to store here.
00:19
Now of course each of the checks that we perform belong to an endpoint, so we'll go ahead and add in a foreign id for the endpoint id here. We'll go ahead and constrain this so it's hooked up to that in the database and really importantly we want to add a on delete cascade so if the endpoint is deleted
00:40
all of the checks get deleted alongside of this. The next thing that we're going to do is create an unsigned integer, so let's choose that and that's going to be the response code or the response status. I'm just going to call it response code and we know that if this check fails for any reason
00:58
we're going to go ahead and store the response body in here and of course we're going to make that nullable because if we have a 200 or any kind of successful response code we're going to go ahead and not store a body so important that is nullable. Okay so for our checks table that's pretty much it so let's go ahead and migrate this out
01:17
and then we're just going to go straight over to the check model and just fill out what we can fill in here or make this completely unguarded so we of course want the response code to be fillable and we want the response body to be fillable as well. While we're in here we'll go ahead and set up the relationship back to the endpoint
01:38
because we know that a check belongs to an endpoint so we may as well add that in here now. Belongs to endpoint and that's done and then we can head over to the endpoint itself and go ahead and add the relationship for our checks so let's go ahead and return very very simple again in terms of the relationships here that this has many checks so we can access them
02:04
as we need now what we're also going to do in here is have the ability to get the last check that was performed now what we of course could do is reference the checks relationship and grab the first one so if we were on an endpoint we could do something like checks and then first but it's a lot more efficient to set up a latest of many relationship in here
02:28
so what we're going to do is create another relationship in here just called check and then we're going to go ahead and say that this has one so it has one check and then what we're going to do is add latest of many so when we access the check relationship just like we normally would as long as we eager load that in we're just going to receive back the latest check that we
02:51
have in terms of the checks that we're storing so that's really really important that we include that so it's a little bit more efficient and to be honest for now that is pretty much it we've got a very simple table out here with the response code and the response body and of course we know what we can do is start to store the data that we get back from the response in this table now
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.