Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #43711, comment 15


Ignore:
Timestamp:
05/30/2018 11:32:19 PM (6 years ago)
Author:
MikeSchinkel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #43711, comment 15

    initial v1  
    55I'd like to throw a new contender into the ring; ''(currently named)'' [https://github.com/wplib/wplib-box WPLib Box] [https://github.com/wplib/wplib-box/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.17.0 0.17.0].
    66
    7 We originally decided to build it because of frustrations with VVV. The fact VVV was provisioned locally using Puppet, which often failed and required sysadmin level skills to debug meant that it was not a solution that developers with few sysadmin skills could trust.  Instead we wanted a box that “just worked,” so we built one that was pre-provisioned.  And as of `0.10.2` it was really solid. That took us about a year, though not full time.
     7We originally decided to build it because of frustrations with VVV. The fact VVV was provisioned locally using a 1000+ line Bash script that takes 30+ minutes to run, which often failed and required sysadmin level skills to debug meant that it was not a solution that developers with few sysadmin skills could trust.  Instead we wanted a box that “just worked,” so we built one that was pre-provisioned.  And as of `0.10.2` it was really solid. That took us about a year, though not full time.
    88
    99Then we set our sites higher and decided to build a box that not only just worked but what capable of running any stack needed while still ensuring the most common use-cases were dead simple. And that lead us to planning the use of a set of orchestrated Docker containers.