[wp-trac] [WordPress Trac] #43711: Let's create a standard development setup for WordPress core.

[WordPress Trac]

#43711: Let's create a standard development setup for WordPress core.
------------------------------+------------------------------
 Reporter:  omarreiss         |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by TJNowell):

 > Weird, maybe I am confusing VIP QuickStart.

 That's correct, VIP Quickstart provisioned via a puppet setup, though VIP
 Quickstart is quite dead

 As a sidenote:

  - VVV 2 is intended to be disposable, you configure what you want and
 provision, and a VM gets created, with the intention that you can throw
 the VM away and recreate it at any time
  - We have Jenkins pre-building base boxes with Ubuntu 14, and are in the
 testing phase prior to merge
  - VVV 2.2.1 now only requires a single vagrant plugin, and updates to the
 Contributor day USB generator now bundle that plugin with the USB drive,
 eliminating all network dependencies
  - It seems Pento has his own solution that installs Node and grunt
 watchers on the host then fires up a docker based WP setup via an electron
 app ( https://github.com/pento/wordpress-development-environment ). The
 irony being that the code could be simplified by swapping the commands for
 vagrant commands as only vagrant up, provision, and halt would be
 necessary

 I appreciate the desire to make getting started with contribution easier,
 but it's clear the existing projects for local dev already have this in
 mind as VVV demonstrates, and as Mike indicated with new versions of WP
 Lib Box.

 What we have here is a conflation of the Travis + PHP 5.2 problem, and
 [https://xkcd.com/927/ this Xkcd comic]. I don't expect that any contender
 will get picked here, either things will remain as they are, or something
 new will be built then used by a minority of people, for which we'll have
 a new support and maintenance burden.

 In the meantime, consider provisioning a more recent build of VVV 2 with
 Vagrant 2.1, VVV is a very different beast internally these days, and a
 lot of issues people remember were resolved years ago

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43711#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform