Some Hosting Features require require a much deeper understanding of Aegir, Drush, Git, and/or Drupal (etc.) to use properly and safely. In addition, a number of features that are currently under 'Experimental' and stable and used in production by most (if not all) core maintainers. We should consider moving these under the 'Advanced' category that I recently added.

Likely candidates:

  1. Web pack
  2. Web clusters
  3. SSL support
  4. NGINX SSL support
  5. Git support
  6. CiviCRM support
  7. Quotas
  8. Sign-up form

Here is my reasoning: (1) and (2) require setting up SSH access for the 'aegir' user, a load balancer, etc. (3) and (4) require replacing self-signed certificates manually. (5) requires manual intervention to run backups, updates, etc. (6) introduces a whole new application to manage, with its own cron queue, etc. (6) and (7) imply more of a self-serve model, which brings with it security and access-control implications.

Comments

ergonlogic created an issue. See original summary.

  • helmo committed f5fd687 on 7.x-3.x
    Issue #2568141: Add advanced to the example code
    
helmo’s picture

gboudrias’s picture

Issue tags: +Aegir 3.2
helmo’s picture

I think hosting_tasks_extra can also go to advanced. http://drupalcode.org/project/hosting_tasks_extra.git/commit/82acb2f

gboudrias’s picture

Features currently in advanced: tasks_extra, hosting_git.

Agreed on the rest. We should probably move backup manager and remote import into Advanced too... Basically everything complicated but stable.

  • helmo committed f5fd687 on 7.x-4.x, aegir4_https
    Issue #2568141: Add advanced to the example code