I updated to origin/production this morning, and it looks like the init:php command does not do anything anymore, but it is still listed as a command. Running ./drupalci init:php gives the following output.

vagrant@vagrant-ubuntu-trusty-64:~/drupalci_testbot$ ./drupalci init:php
Executing init:php
PHP Notice:  Undefined index: all in /home/vagrant/drupalci_testbot/src/DrupalCI/Console/Command/Init/InitPhpContainersCommand.php on line 113
PHP Notice:  Undefined index: all in /home/vagrant/drupalci_testbot/src/DrupalCI/Console/Command/Init/InitPhpContainersCommand.php on line 115
Please select the numbers corresponding to which DrupalCI web environments to support. Separate multiple entries with commas. (Default: [])
  [0] all
 > 0
No valid php container names provided. Aborting.

Comments

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Component: DrupalCI console script » Vagrant/Local Testing

  • Mile23 committed 876971e on 2514034-remove-init-php 
    Issue #2514034: Removed InitPhpContainersCommand, amended support code...
mile23’s picture

mile23
Primary language English
Location Seattle, WA
commented
Status: Active » Needs review

We have init:web for getting the PHP containers, and the containers are named web-5.5, etc. So therefore: Goodbye init:php!

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented

yep. this is good. expunged, and merged into dev.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Status: Needs review » Fixed
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented

Status: Fixed » Closed (fixed)

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