Furthermore, when operating in a container-based microservices architecture, there must be a way to routinely execute a plethora of 'maintenance' scripts.
Instead of doing this in a singular, monolithic environment where you would program the Linux '''cron''' system to handle the queue; and use SSH and shell commands to execute maintenance scripts, you need a way to invoke a service container that has full "knowledge" of the primary application and service endpoints but is NOT used for handling web requests. In a restaurant analogy, it is not the wait staff serving customers at the restaurant, or even the chef cooking food. It is taking care of inventory, menu offerings, seating, staffing and schedules, and dishes etc (the manager, the hostess, bus boy and dishwasher). In a Docker environment, setting up a [[mediawikiwiki:MediaWiki-Docker/Configuration_recipes/Jobrunner|Jobrunner container]] is exactly how it's done in [https://github.com/wikimedia/mediawiki-docker/tree/master MediaWiki Docker. ]
==Requirements==
