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
29. Authorizing the endpoint details
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
A really quick fix before we finish up on our endpoint index just here, this one, we didn't authorize this request. Now we know that over on our endpoint policy, we have the ability to update, destroy or check against this. We want to add one in here to say
00:18
can we view this or show this. So I'm going to go ahead and call this show, I think that makes sense, or list or whatever you want to call it. You could even create a generic touch to see if a user just has permission in general. So let's call this show and from the endpoint that we get passed in, of course the check is exactly the same here, we just want to make sure that the user has access
00:41
to this via the site that they own. So now that that's in there, we can go ahead and authorize this. Now of course you can authorize this directly within the controller, so we could say can we show this endpoint and that would work as normal. So we see that we've got permission to do this and if the id differs then it's not going to work. But again across our app we've been using
01:03
form requests, so I always like to keep things as consistent as possible and even if we're not posting through here, we can still create a form request to at least authorize this. So let's go ahead and do that now. Let's create out a form request here and keep the naming convention the same. If we look at the form request that we've got already, it's endpoint destroy controller,
01:22
endpoint store controller update. So we're gonna name this, if we just go ahead and make out a request here, endpoint and we could say endpoint index request. I think that actually makes a little bit more sense because technically this is an index, but then again we're showing this via root model binding. So yeah let's keep this to show, endpoint show controller request. I think
01:48
that makes a lot more sense. Okay so we can swap this out straight away. Endpoint show request and we're done. So we can go into here and the rules obviously we don't care about because we're just getting this, but from here we can do exactly the same thing. So this user can show this endpoint. So now everything is nicely tucked away in a form request. Our controller here is nice and clean.
02:12
I'll get rid of the eager loading note because we're going to come back to that later and there we go. So if we come over, sure enough it still works. So a quick fix up there. Of course that's really important because otherwise anyone would be able to type in any endpoint id and see information about that, which is not good.
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.