This project is not covered by Drupal’s security advisory policy.

The experimental Commands module provides a queue of server commands to run on the back-end while logging output to the front. Think Jobs, Pipelines, or Actions but in Drupal.

It can be used to provide a history of commands and their output within the site itself.

This is a proof-of-concept for a modern replacement for DevShop & Aegir's Hosting Tasks module.

Supporting this Module

SEEKING MAINTAINERS. This is a prototype project. If you support the idea of a new hosting system, please get in touch through the issue queues.

TODO

I originally created this in the Operations project, on a feature branch. It was called "Tasks". See here: https://github.com/operations-project/operations/tree/feature/tasks/src/...

  • Rename from "Tasks" to "Commands".
  • Move to this git repo.
  • Command bundle classes.
  • User interface work.
  • Documentation.
  • Tests.

Features

  • "Command" entities can be created by users.
  • "Command Types" (Bundles) define what is run and how.
  • Drush command executes the command and logs the results to the entity.
  • Command view page shows the output and status.

More info coming soon.

Supporting organizations: 
ThinkDrop

Project information

  • caution Seeking new maintainer
    The current maintainers are looking for new people to take ownership.
  • Ecosystem: Operations: Drupal for Ops, DevShop
  • Created by jon pugh on , updated
  • shield alertThis project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.

Releases