After installing Aegir, if one navigates to Platforms » Add platform, the only option for platform installation is:

  • Deploy from makefile

This is problematic because:

  • Nobody actually uses Drush Make anymore for maintaining Drupal sites.
  • No modern options are available.
  • There's no indication anywhere on the form that additional options (a) are available and (b) need to be enabled.

Proposal

1. Provide modern options for creating platforms on installation immediately after Aegir installation by enabling the following by default:

  • Composer Deploy via Packagist [hosting_platform_composer]
  • Composer Deploy via Git [hosting_platform_composer_git]
  • Git Deploy (without Composer) [hosting_platform_git]

It should be noted that Git Deploy (hosting_platform_git) is a safer default than Aegir Hosting Git (hosting_git) because the former doesn't allow dangerous operations (e.g. git pulling). If folks actually want to enable these types of things, they can do so by opting in, enabling the other Git module.

These modules depend on Aegir Deploy, which cleans up the Create Platform form, so it'll be enabled automatically.

2. Indicate that other deployment strategies are available and can be enabled.

Discussion and feedback would be appreciated.

CommentFileSizeAuthor
#5 hostmaster-3051058-enable_git_and_composer_platform_options_by_default.patch809 bytescolan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

colan created an issue. See original summary.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Consensus Enterprises, Colan Schwartz Consulting, Aegir Cooperative commented
Issue summary: View changes

Added clarification about why we should choose one Git module over the other.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic at Consensus Enterprises commented

Nobody actually uses Drush Make anymore for maintaining Drupal sites.

Not Drupal 8, but I believe it's still pretty standard for D7 sites, which'll still be around for a few more years.

I don't think "Composer Deploy via Packagist" is particularly relevant for most users. So I'd suggest dropping that one.

helmo’s picture

helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commented

I also do believe makefiles are still used in D7 workfows ... but agree that it's time to have more options by default enabled.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Consensus Enterprises, Colan Schwartz Consulting commented
Status: Active » Needs review
FileSize
hostmaster-3051058-enable_git_and_composer_platform_options_by_default.patch809 bytes

I added two from the list above, leaving out the Packagist one. I didn't touch the makefile one; so that should still be there.

  • colan committed 8e4647d on 7.x-3.x 
    Issue #3051058 by colan, helmo, ergonlogic: Enabled modules Composer...
colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Consensus Enterprises, Colan Schwartz Consulting commented
Status: Needs review » Fixed

Works well in the Aegir dev VM.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
CreditAttribution: colan at Consensus Enterprises, Colan Schwartz Consulting commented

For future reference, I added a link to the docs (for more info & adding other methods) on the Add Platform page. See https://git.drupalcode.org/project/hosting_deploy/commit/51515e3 for details.