Using Aegir 3.173 (deb package on Ubuntu) and hosting_deploy 7.x-3.1.

If I create a platform "mydrupal8" from a local drush makefile, everything works fine: The platform directory is created at /var/aegir/platforms/, the platform is created with all its modules, sites can be created using the platform, I can run composer as user aegir in /var/aegir/platforms/mydrupal8 to add new modules or libraries which then appear in all sites created with that platform, etc..

Now, I tried to create platforms using the strategy "None (not managed by Aegir)". I was assuming that creating a platform that way would be the most basic of all platform creation processes: something like create a few hooks in the database and create a directory into which one would later drop its code.

But it fails consistently.

If I try to create a platform "strategy-none" using deployment strategy "None (not managed by Aegir)", the verify task fails with errors:

Platform makefile: - debug
We could not find an applicable site for that command. - error
Drush could not bootstrap the platform at /var/aegir/platforms/strategy-none. Please check the platform directory exists and is readable. The errors were: DRUSH_NO_SITE: We could not find an applicable site for that command. - error

Full task log message attached.

Not sure what happens there.

After task has failed, there is no directory /var/aegir/platforms/strategy-none

I get similar errors when trying to create a platform using "Deploy a Composer project from a Packagist repository", even with a project that does not require drush 9, but I was assuming I was doing something wrong and kept researching and trying various things.

But maybe the problem is elsewhere if I cannot even create a platform with the "None" strategy?

Any help and hints greatly appreciated.

PS additional info, just in case it could be relevant:
I can install modules and libraries in a platform with composer (e.g. as user aegir, running composer inside /var/aegir/platforms/myplatform/)
but
I cannot install anything on hostmaster with composer (i.e. as user aegir, running composer inside .var/aegir/hostmaster-7.x-3.173/) - composer runs but fails to find the modules.

CommentFileSizeAuthor
platform-strategy-none-creation-fails.pdf70.97 KBagaq
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

agaq created an issue. See original summary.

agaq’s picture

Title: Fail to create a platform using deployment strategy "None (not managed by Aegir" » Fail to create a platform using deployment strategy "None (not managed by Aegir)"
Issue summary: View changes
colan’s picture

I get similar errors when trying to create a platform using "Deploy a Composer project from a Packagist repository", even with a project that does not require drush 9, but I was assuming I was doing something wrong and kept researching and trying various things.

This sounds like #3038831: deployfrompackegist error.

I cannot install anything on hostmaster with composer (i.e. as user aegir, running composer inside .var/aegir/hostmaster-7.x-3.173/) - composer runs but fails to find the modules.

Composer isn't really supported in Drupal 7 so I wouldn't expect that to work.

Let's keep this issue focused on the None strategy, which I can't really comment on because I didn't work on it, and haven't used it. I'll ping @ergonlogic, who worked on it.

agaq’s picture

Composer isn't really supported in Drupal 7 so I wouldn't expect that to work.

So should we remove the composer install instructions at https://www.drupal.org/project/hosting_deploy/releases/7.x-3.1? The page shows:

Install with Composer: $ composer require 'drupal/hosting_deploy-hosting_deploy:^3.1'

And by the way, should it be 'drupal/hosting_deploy-hosting_deploy' or 'drupal/hosting_deploy'? (I had tried both)

Should I open a new ticket about that? (still learning how to use the ticket system, and its etiquette)

ergonlogic’s picture

Recall that the deploy strategies are ways of building a Drupal code-base.

"None" here means that Aegir won't attempt to deploy a platform at all. That is, it assumes that the platform has already been built by some other means, and is simply registering it within Aegir, scanning it for packages, etc.

So should we remove the composer install instructions at https://www.drupal.org/project/hosting_deploy/releases/7.x-3.1? The page shows:

Install with Composer: $ composer require 'drupal/hosting_deploy-hosting_deploy:^3.1'

I believe those instructions are automatically generated by drupal.org to show how to add a project to a Composer-managed Drupal codebase.

And by the way, should it be 'drupal/hosting_deploy-hosting_deploy' or 'drupal/hosting_deploy'? (I had tried both)

Neither. hosting_deploy is a module, not a distribution. Instead, take a look at the Thunder or Open Social distributions and the Composer installation instructions for Thunder and Open Social.

Based on those, try either burdamagazinorg/thunder-project or goalgorilla/social_template.

agaq’s picture

Sorry about the confusion. I was mentioning drupal/hosting_deploy in passing (and only to note that the syntax looked suspicious), in relation to my remark:

PS additional info, just in case it could be relevant:
I can install modules and libraries in a platform with composer (e.g. as user aegir, running composer inside /var/aegir/platforms/myplatform/)
but
I cannot install anything on hostmaster with composer (i.e. as user aegir, running composer inside .var/aegir/hostmaster-7.x-3.173/) - composer runs but fails to find the modules.

I was not trying to create a platform with it. For that I had tried acquia/lightning-project, hughestech/lightning-project, drupal-composer/drupal-project and drupalwxt/wxt-project using "Deploy a Composer project from a Packagist repository" deploy strategy.

I will now try to create a platform from one of these projects directly on the command line, then use the "None" strategy to register it with aegir.

colan’s picture

Status: Active » Needs review

  • 51515e3 committed on 7.x-3.x
    Issue #3038678 by colan: On Add Platform page, added link to...
colan’s picture

Status: Needs review » Closed (works as designed)

The above commit should help as it links the Add Platform page to Deployment Strategies in the docs.

See also #3065370: Make the default option in hosting_deploy_platform_deploy_strategies() user friendly.

colan’s picture

Status: Closed (works as designed) » Fixed

Status: Fixed » Closed (fixed)

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