Part 2 - Creating Our First Controller

Getting Started

All controllers are located in the app/http/controllers directory and Masonite promotes 1 controller per file. This has proven efficient for larger application development because most developers use text editors with advanced search features such as Sublime, VSCode or Atom. Switching between classes in this instance is simple and promotes faster development. It's easy to remember where the controller exactly is because the name of the file is the controller.

You can of course move controllers around wherever you like them but the craft command line tool will default to putting them in separate files.

Creating Our First Controller

Like most parts of Masonite, you can scaffold a controller with a craft command:

$ craft controller BlogController

This will create a controller in app/http/controllers that looks like:

class BlogController:
    ''' Class Docstring Description '''

    def show(self):
        pass

Simple enough, right?

Notice we now have our show method we specified in our route.

Returning a View

We can return a view from our controller. A view in Masonite are html files. It is what the user will see. We can return a view by using the view() function:

def show(self):
    return view('blog')

Notice here we didn't import anything. Masonite comes with several helper functions that act like built in Python functions. These helper functions make developing with Masonite really efficient.

Creating Our View

You'll notice now that we are returning the blog view but it does not exist.

All views are in the resources/templates directory. We can create a new file called resources/templates/blog.html or we can use another craft command:

$ craft view blog

This will create that file for us.

If we put some text in this file like:

This is a blog

and then run the server

$ craft serve

and open up localhost:8000/blog, we will see "This is a blog"