Add Tide as an installable or maybe as a stack.

Looking more at this, it seems that Tide attempts to recreate much of what WPLib Box does, so implementation by nature would be to simplify Tide significantly and replace much of its ad-hoc implementations with general purpose box functionality configured for Tide use.

For example, Tide has a complex template build system because of it's decision to use docker-compose. The Box's "stack" system allows for dynamic containers that can eliminate the need for a build system and use a simple list of Docker components instead that read the .env file directly.

For another example Tide includes an "API container" that is really just a WordPress install with a LEMP server and several plugins. That can easily be an installable stack that just extends the default WordPress stack.

All-in-all, Tide could be made to be plugin-and-play aside from filling out the .env file if implemented in WPLib Box.

(Maybe the Tide people might even recognize this and just ship the local Tide development environment packaged inside of WPLib Box?)

wplib / wplib-box

Add Tide as an installable or maybe as a stack. #410