In the Part 8, I looked at to adding a logging service provider with the help of a third-party package called Monolog. In this tutorial I’m going extend Joomla’s Github package to integrate some missing (at the time of writing) functionality.
In the Part 7, I looked at how the Github service provider could access configuration and command line input parameters using the DI container. In this tutorial I’m going to look at how I added a logging service provider.
In the Part 6, I looked at how to make a simple configuration service provider. In this tutorial I’m going to look at how to use that configuration data in another service provider.
In the five previous tutorials, I laid the foundations for a command line application built on the Joomla Framework and Composer. In this tutorial I’ll look at adding a service provider to load configuration for the application.
In part 4 we set up a service provider for a Github connector in our command line application using the Joomla Framework’s DI package stack. In this tutorial we’ll look at how to wire it up and test that it all works.
In part 3 we added Joomla Framework’s DI and Github package to our stack via Composer. In this tutorial we’ll look at how to add the Github connector as a service for the application to use when it needs it.
In part 1 and part 2 we looked at how to get a command line application set up using the Joomla Framework and Composer. Any good chef has plenty of herbs and spices to choose from when cooking a master dish, so now it’s time to add some more tools to our application stack.