|
|
**NOTE:** This is a proposal for AegirNG Architecture by @ergonlogic and @colan. Please visit https://www.drupal.org/node/2714641 to discuss further.
|
|
|
# Introduction
|
|
|
|
|
|
For an overview of Aegir, please see [the Wikipedia page](https://en.wikipedia.org/wiki/Aegir_Hosting_System). This is a proposal for the next-generation Aegir 5 architecture by @ergonlogic and @colan. Please visit [the meta issue](https://www.drupal.org/node/2714641) for discussion.
|
|
|
|
|
|
*For information on the current stable release (Aegir 3), please visit [aegirproject.org](https://www.aegirproject.org/).*
|
|
|
|
|
|
# Summary
|
|
|
AegirNG is made up of several components. First off, there is a front-end built on Drupal 8. This user interface passes configuration variables into a distributed task queue, built on Celery. Finally, queue workers receive these tasks, and run various operations, based on the variables passed into the task from the front-end. A command-line client, built on Drupal Console, can also post tasks to the queue, allowing for relatively simple scripting.
|
... | ... | |