VVV specific dockerfile, gets built on provision

[tomjn]

Moves the dockerfile from pentatonic funk over to VVV, this does centralise things here, though ideally we build this and put it up as an image with a VVV name. I also used vvv@tomjn.com but that's only slightly less problematic ( is it optional? ).

The other Q is, what can we put in here to save time during the main VVV provisioner that only docker can do? Do we need a compose file to setup Nginx/MariaDB containers and would that mean changing other parts of VVV to make that work? Would all wp-config.php files need to change on docker based setups?

Checks

• I've updated the changelog.
• I've tested this PR
• This PR is for the develop branch not the stable branch.
• This PR is complete and ready for review.

[update-docs]

Thanks for opening this pull request! Make sure CHANGELOG.md gets updated with this change, additionally any docs that need updated can be found at https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org

GitHub

GitHub - Varying-Vagrant-Vagrants/varyingvagrantvagrants.org: The VVV docs and website

The VVV docs and website. Contribute to Varying-Vagrant-Vagrants/varyingvagrantvagrants.org development by creating an account on GitHub.

[tomjn]

I'm thinking this could be expanded to execute the main provisioner, and perhaps some of the tools provisioner ( parts that don't use shared/mapped folders at runtime ). Then this could be set on a toggle/switch as a way to build a VVV container for a stable version