Feat/localwp - Githubissues

This PR introduces Spinup Local WP.

I extracted our WordPress backend-starter, minus the Bedrock/WordPress installation folder, into a separate, standalone NPM package. This makes our Docker setup maintainable from a single source of truth, and simplifies the dev experience for CloakWP users, also making it more approachable. The downside for end-users is that it removes their code ownership and control over the Docker configuration; but my hypothesis is that most devs don't want to or know how to work directly with Docker, and would prefer a magic abstraction that just works; we can add more package configuration options over time to allow more control over the Docker config, or users who really want that control can simply opt-out of using Spinup Local WP and use their own Docker system.

Couple nice things this introduces:

Simpler folder/file structure for WordPress backends -- it's now just the typical Bedrock folder, with an added package.json (in order to install Spinup Local WP). This also makes manual installations much simpler, since you can run composer create-project roots/bedrock to spin up a new Bedrock project, and then you just need to run npm init and npm install @cloakwp/spinup-local-wp (all of which could be easily abstracted into one command in the future)
There's no longer a need for two .env files (previously had one for Docker, one for WordPress... which was confusing).

cloak-labs / cloakwp-workspace

Feat/localwp #2

⚠️ No Changeset found