... | ... | @@ -40,9 +40,9 @@ The back-end will be implemented as a Celery queue worker. This can then easily |
|
|
|
|
|
We can write small Ansible roles to represent each task we want to implement, rather than the usual model of handling all tasks related to a given application. A small set of variables will need to be mapped to the equivalent front-end fields.
|
|
|
|
|
|
For example, a task on the front-end to deploy a Drupal codebase, could trigger a `aegir.drupal8-codebase-git-deploy` role, where we provide variables for a git repo from whence to clone, as well as a filesystem path where it should be deployed.
|
|
|
For example, a task on the front-end to deploy a Drupal codebase, could trigger a `aegir.DeployDrupal8GitPlatform` role, where we provide variables for a git repo from whence to clone, as well as a filesystem path where it should be deployed.
|
|
|
|
|
|
A separate `aegir.drupal8-codebase-verify` task could then ensure that proper file ownership and permissions are maintained. This should only require a path variable to be passed to the task. (note: we may not *need* verify anymore; this is just an example)
|
|
|
A separate `aegir.VerifyDrupal8Platform` task could then ensure that proper file ownership and permissions are maintained. This should only require a path variable to be passed to the task. (note: we may not *need* verify anymore; this is just an example)
|
|
|
|
|
|
## Security model
|
|
|
|
... | ... | |