search

alnutile / behat-vagrant

Installs a complete preconfigured environment to use the behat_editor, behat_editor_saucelabs and behat_editor_github modules
GNU General Public License v2.0
4 stars 2 forks source link

configure-composer-module errors on install #12

Open niccolox opened 10 years ago

niccolox commented 10 years ago

hi

I am getting errors on install

I tried the troubleshooting in the readme

very promising project btw !

Error executing action run on resource 'bash[configure-composer-module]'

Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received '1' ---- Begin output of "bash" "/tmp/chef-script20140426-1281-vsrepu-0" ---- STDOUT: The following extensions will be enabled: composer_manager Do you really want to continue? (y/n): y One or more extensions have dependencies managed by Composer. Update packages managed by Composer? (y/n): y The composer.json file is missing. Would you like to re-build it? (y/n): y Download and install Composer? (y/n): y

!/usr/bin/env php

All settings correct for using Composer Downloading...

niccolox commented 10 years ago

vagrant ssh Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64)

alnutile commented 10 years ago

Sorry about the delay on the reply. The best thing to do with drupal and composer (and I will post this later in the docs) is to run 

composer --working-dir=/path/to/composer/folder/wtih/composer/json/file update

This keeps drupal out of the picture.

The error you got tends to be a drupal registry rebuild issue you can quickly fix with drush rr

alnutile commented 10 years ago

here is a quick post on it http://www.alfrednutile.info/posts/65

frederickjh commented 10 years ago

Hi!
I too am having this problem. I think that this is related to the following Composer Manager module issue: Drush make file support?

cpliakas commented 10 months ago

The challenge that I see is that the consolidated composer.json file is generated from modules that are installed. Since drush make runs outside of a Drupal bootstrap because it is building the distro, Composer Manager will have not generated the composer.json file so there will be no dependencies to resolve.

In the current module, you have to run drush make, then run through the installation profile and enable modules, and then run Composer either via Drush or manually. Unfortunately it cannot be run in a different order unless the distro comes with a prebuilt composer.json file.

The possible solution: cpliakas commented 6 months ago

After some investigation, it looks like the error you are experiencing was addressed in #2199677: Error thrown when running drush omposer-manager install the first time.

I have been using Composer Manager with Drupal apps build with a make file workflow, and now everything seems to be working fine. The key is to run drush make, drush site-install, and then composer install. Unfortunately given how things currently work you need that extra step as drush make is just a build process and Composer Manager has to do it's thing when your Drupal site and modules are installed.

cpliakas also shared a related issue: #1979822: Explore integration with the Composer Manager module The fix for this was commited on 2014-02-21. There is a newer releas of Composer Manager than the version 7.x-1.0-rc1 that is being used in your vagrant installation.

So it looks like a newer version of Composer Manager so it does not throw an error, a prebuilt composer.json file or running the commands in the proper order are needed to make this work.

Frederick

alnutile commented 10 years ago

Hello, At this point it might be best for someone to fork this. I think this vagrant build is not as good as say http://laravel.com/docs/homestead with a decent composer install for the behat side of things.

Also the behat included here is v1 and the code base was a bit hard to install.

v2 is all composer and Laravel so is easier to install.

But it will not be ready for a bit.

This is a great seed example as well alnutile/behat-seed