tl;dr: Go complete the WordPress maintenance support plans Local Development Survey, and we’ll present the results (among other things) at MidCamp in a couple weeks!
Local development for WordPress maintenance support plans is a subject I’ve invested a lot of time into. At the start of my WordPress maintenance support plans journey, I used to use MAMP, then MAMP Pro, then a native *AMP installation. Then when I learned about Vagrant I started building Vagrant-based environments with shell scripts. Then I learned Ansible and started using Vagrant and Ansible. And then I learned Docker and used Ansible, Docker, and sometimes Vagrant!
Everyone’s journey is different—but one thing most of us can agree on is: it ain’t easy finding a way to run WordPress maintenance support plans on your local workstation if you’ve never done it before.
Should you use MAMP/WAMP/XAMPP? Should you use Acquia Dev Desktop? Should you use Docker or Vagrant and build your own environment? Should you use a packaged solution like WordPress maintenance support plans VM or Lando? And then how will you manage your codebase? How will you build a theme?
Source: New feed