PHPackages                             linkorb/commando - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues & Workers](/categories/queues)
4. /
5. linkorb/commando

ActiveApplication[Queues & Workers](/categories/queues)

linkorb/commando
================

Commando: Execute Commands from Queues

v1.14.0(6y ago)31631[5 PRs](https://github.com/linkorb/commando/pulls)MITPHP

Since Nov 29Pushed 2y ago3 watchersCompare

[ Source](https://github.com/linkorb/commando)[ Packagist](https://packagist.org/packages/linkorb/commando)[ Docs](https://github.com/linkorb/commando)[ RSS](/packages/linkorb-commando/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (4)Dependencies (12)Versions (21)Used By (0)

Commando
========

[](#commando)

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`:

```
commands:
  hello:
    template: echo "Hello {{ greeted }}"
    inputs:
      greeted:
        default: world
```

2. Your app writes a job into `/your/commando-path/new` called `1.json`:

```
{
  "command": "hello",
  "inputs": {
    "greeted": "universe"
  }
}
```

3. You (or cron) runs `commando run`.
4. 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"`
5. Commando reports the job status back to the store, including exit codes, start/end times, total duration, and stdout and stderr
6. Your app reports back to the user if needed, based on the status report.

Stores:
-------

[](#stores)

- `JsonDirJobStore`: Manages jobs through json files with a simple directory structure
- `PdoJobStore`: Manages jobs through a database table
- `CamundaJobStore`: Camunda External Task client

Use-cases
---------

[](#use-cases)

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:

Examples:

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

Conventional Commits
--------------------

[](#conventional-commits)

This repository is using [Conventional Commits](https://www.conventionalcommits.org/)

Please run `npm install` at least once, in order to install the appropriate tooling and git hooks (this helps you to follow the conventions by linting them before actually committing).

In short: you should prefix your commit titles with the correct type (i.e. `feat: my new cool feature`). This helps to create clear commit histories, automatically handles semver, tagging and CHANGELOG.md generation.

If you'd like to reference a card in our planning system, simply add a `#123` to the end of your commit title. The card will be correctly linked from the changelogs etc.

To publish a new release, simply run `npm run publish`. This will update the changelog, and manifests like composer.json, package.json, etc to a new tag. The tag follows Semver, and is selected based on your commit types since the last release.

License
-------

[](#license)

Please refer to the included LICENSE.md file

Brought to you by the LinkORB Engineering team
----------------------------------------------

[](#brought-to-you-by-the-linkorb-engineering-team)

[![](https://camo.githubusercontent.com/62fb66b034de7ea7fca9fd9776424b5348daa76ef8622caf92c2f7622003e5ef/687474703a2f2f7777772e6c696e6b6f72622e636f6d2f642f6d6574612f74696572312f696d616765732f6c696e6b6f7262656e67696e656572696e672d6c6f676f2e706e67)](https://camo.githubusercontent.com/62fb66b034de7ea7fca9fd9776424b5348daa76ef8622caf92c2f7622003e5ef/687474703a2f2f7777772e6c696e6b6f72622e636f6d2f642f6d6574612f74696572312f696d616765732f6c696e6b6f7262656e67696e656572696e672d6c6f676f2e706e67)
Check out our other projects at [engineering.linkorb.com](http://engineering.linkorb.com).

Btw, we're hiring!

###  Health Score

33

—

LowBetter than 75% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity72

Established project with proven stability

 Bus Factor1

Top contributor holds 87.5% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~74 days

Recently: every ~23 days

Total

15

Last Release

2416d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/1db66b320db18b8036ea68211b7d8a39e7c6da97e6fd29f59a50380ebb69d0bb?d=identicon)[joostfaassen](/maintainers/joostfaassen)

---

Top Contributors

[![joostfaassen](https://avatars.githubusercontent.com/u/411113?v=4)](https://github.com/joostfaassen "joostfaassen (42 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (6 commits)")

---

Tags

queuegitcommandlinkorbcamundacommando

### Embed Badge

![Health badge](/badges/linkorb-commando/health.svg)

```
[![Health](https://phpackages.com/badges/linkorb-commando/health.svg)](https://phpackages.com/packages/linkorb-commando)
```

###  Alternatives

[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.4k5.6M651](/packages/sylius-sylius)[shopware/platform

The Shopware e-commerce core

3.3k1.5M3](/packages/shopware-platform)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.3M152](/packages/sulu-sulu)[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[contao/core-bundle

Contao Open Source CMS

1231.6M2.4k](/packages/contao-core-bundle)[shopware/core

Shopware platform is the core for all Shopware ecommerce products.

595.2M386](/packages/shopware-core)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)