Service Providers

Service Providers are the key building blocks to Masonite. The only thing they do is register things into the Service Container, or run logic on requests. If you look inside the config/providers.py file, you will find a PROVIDERS list which contains all the Service Providers involved in building the framework.
Although uncommon, You may create your own service provider and add it to your providers list to extend Masonite, or even remove some providers if you don't need their functionality. If you do create your own Service Provider, consider making it available on PyPi so others can install it into their framework.
Creating a Provider
We can create a Service Provider by simply using a craft command:
1
$ python craft provider DashboardProvider
Copied!
This will create a new Service Provider under our app/providers/DashboardProvider.py. This new Service Provider will have two simple methods, a register method and a boot method. We'll explain both in detail.
Service Provider Execution
There are a few architectural examples we will walk through to get you familiar with how Service Providers work under the hood. Let's look at a simple provider and walk through it.
1
from masonite.providers import Provider
2
​
3
​
4
class YourProvider(Provider):
5
    def __init__(self, application):
6
        self.application = application
7
​
8
    def register(self):
9
        self.application.bind('User', User)
10
​
11
    def boot(self):
12
        print(self.application.make('User'))
Copied!
We can see that we have a simple provider that registers the User model into the container. There are three key features we have to go into detail here.
Register
In our register method, it's important that we only bind things into the container. When the provider is first registered to the container, the register method is ran and your classes will be registered to the container.
Boot
The boot method will have access to everything that is registered in the container. The boot method is ran during requests and is actually resolved by the container. Because of this, we can actually rewrite our provider above as this:
1
from masonite.provider import ServiceProvider
2
from app.User import User
3
​
4
class UserModelProvider(ServiceProvider):
5
    ''' Binds the User model into the Service Container '''
6
​
7
    def __init__(self, application):
8
        self.application = application
9
​
10
    def register(self):
11
        self.application.bind('User', User)
12
​
13
    def boot(self, user: User):
14
        print(user)
Copied!
This will be exactly the same as above. Notice that the boot method is resolved by the container.
Registering the Service Provider
Once you create your own service provider, it will need to be registered in the PROVIDERS list. This is likely in your config/providers.py file:
1
PROVIDERS=[
2
    #..
3
    UserModelProvider,
4
]
Copied!
Once registered it will take your register and boot method into account when the framework boots up or registers.

Features - Previous

Validation

Next - Architecture

Service Container

Last modified 26d ago

Export as PDF

Copy link

Contents

Creating a Provider

Service Provider Execution

Boot

Registering the Service Provider