Restricting routes based on roles is a handy feature to have. An easy way to acheive this is using a middleware that checks the user’s role to decide if they have access to it. In this post we will go over creating a middleware to allow us to restrict routes to specific roles.
**This assumes you already have Laravel installed on your machine and know how to create a basic application using it**
Let’s get started.
I had the need to be able to deploy a Laravel based application to an IIS server that was shared by many basic PHP applications without monopolizing the entire server instance like most deployment guides cover. I figured out that you can create an Application inside IIS, point to the /public folder in the Laravel application, and with some routing defined in a web.config you can get the application serving properly from subpath.
**This assumes you already have Laravel installed on your machine and know how to create a basic application using it**
**This also assumes you have IIS setup already to serve basic PHP 7.x applications**
Let’s get started.
Happy First Post 😀
Staring Sinistar from 1982.
THX Blog 