Commando: Execute Commands from Queues

Installs: 112

Dependents: 0

Suggesters: 0

Stars: 1

Watchers: 3

Forks: 0

Open Issues: 0


v1.8.0 2018-08-15 20:09 UTC


Commando is a generic job-runner.

You can define your own commands in Json or Yaml files, and process jobs from different stores such as a directory of files, or a database.

It's goal is to make it easy to implement background jobs into your application.

An example workflow:

  1. You define a command "hello" in commando.yml:
    name: hello
    template: echo "Hello {{ greeted }}"
        name: greeted
        default: world
  1. Your app writes a job into /your/commando-path/new called 1.json:
  "command": "hello",
  "arguments": {
    "greeted": "universe"
  1. You (or cron) runs commando run.
  2. Commando will check for new job files in the configured store (in this case a directory), execute the command, replacing arguments in the template with the passed job arguments, finally executing echo "Hello universe"
  3. Commando reports the job status back to the store, including exit codes, start/end times, total duration, and stdout and stderr
  4. Your app reports back to the user if needed, based on the status report.


  • JsonDirJobStore: Manages jobs through json files with a simple directory structure
  • PdoJobStore: Manages jobs through a database table


You can replace the template with much more complex command-lines or shell-scripts.

Your app should treat these jobs as "fire-and-forget", meaning the app should not block, waiting for response. It's most ideal in scenarios where your triggers commands and doesn't need to know about the response right away:


  • Update PDFs or reports in the background
  • Send emails and notifications
  • Create a database backup
  • Process uploaded image files
  • ...etc


Please refer to the included file

Brought to you by the LinkORB Engineering team

Check out our other projects at

Btw, we're hiring!