[wp-trac] [WordPress Trac] #43711: Let's create a standard development setup for WordPress core.
WordPress Trac
noreply at wordpress.org
Wed May 16 13:31:26 UTC 2018
#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):
Keep in mind that when using docker with Vagrant actually runs inside a
Virtualbox VM. Under MacOS native docker uses an xhyve VM running Alpine
Linux, and under Windows it's an Alpine Linux VM under a Hyper-V managed
VM.
I'm mindful that in the future, we'll be told that docker containers are
the only option, and that other methods will suffer from this. I'm also
disappointed that Travis limitations are dictating local dev environment
decisions. If docker is the solution there, then fine, but that's not the
same issue as a standardised development environment.
Before we blindly charge down this route, I'd like to see a solution to
making contributer day attendees pay for and download a Windows upgrade
since Hyper V is required for Docker on Windows, and it requires Windows
Enterprise/Professional. Docker is not as inclusive or available as it
appears, and it's being touted as a way to make contributing for new users
easier, which isn't necessarily true.
Any solution would require a provisioning script to set up the database
user and the relevant files, as well as perform checks that relevant tools
are installed. This would seem to be a more portable approach that needs
to be taken anyway regardless of what devops gets done.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43711#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list