Creating MunkiReport Modules Part 3

05 December 2018 on macOS and MunkiReport. 3 minutes

Part 1 Getting Started Part 2 Module Structure

Module Deployment Process

For years, modules have been included into the core of MunkiReport. It has lowered the bar for admins to simply install and have things work, but it has slowed development of both the core and modules as the complexity and pace of development has risen. Adding custom modules has always been possible, but decoupling modules from the core truly allows us to have a supported workflow for adding and updating modules outside of the MunkiReport repo.

The process outlined below may not be for everyone. It is not a prereq to creating your own modules. Some may find in useful in certain situations, but it is by no means necessary!

The process utilizes Composer, GitHub, and Packagist.


Composer is a dependency manager for PHP.


We don’t really have to worry about this at the moment. MunkiReport uses it in the background. Occasionally we need to run composer, but we’ll discuss that later.


First of all, if you don’t have an account, go make one. Modules are now separated into their own dedicated repo. Simple enough to do:


Create the repository sans readme and license and from your custom_modules/awesome directory run:

git init
git add .
git commit -m "First commit"
git remote add origin
git push -u origin master

Many users will be able to stop here. You can add commits to your module and when it is needed simply clone or download the files.

Packagist Deployment

You will probably want to bookmark this next part until the module is more complete and ready for deployment, but feel free to read as an overview of the process. The following process is not required to make your own module, but can be helpful in understanding the current deployment process of MunkiReport modules.

Once the module is functional we will create a release for this module:



Packagist is the main Composer repository. To add our release to Packagist, submit the package here:

Add the link to the GitHub repo in the Repository URL and click submit. You may see this:


Oh noes! Will I actually have to talk to Bochoven?! Well, if you want it to be part of the MunkiReport repositories, yes. But luckily, we just need to change this line in our composer.json file for the repo:

"name": "munkireport/awesome",

To our namespace:

"name": "joncrain/awesome",

Once you check again, you may get a warning that your package has a similar name to another package, and if you’re ok with that just continue. It will do more magic and you will see this:


Once we add our release to Packagist we are able to require our module by running the following command to add it to our composer.local.json:

COMPOSER=composer.local.json composer require joncrain/awesome:^1.0

More in this Series


Creating MunkiReport Modules Part 2

In part I we made an awesome module. Or we made the framework for an awesome module. Or really we got ourselves ready to make an awesome module with the awesome built in MunkiReport tools. In this article, we deep dive into the module itself.