Open ottok opened 7 years ago
Other commonly used Vagrant boxes are Flywheel Local and Scotchbox https://scotch.io/bar-talk/announcing-scotch-box-30-and-scotch-box-pro
And a Docker based one: https://github.com/10up/wp-local-docker-v2
And now also from WP Engine: https://wpengine.com/devkit/
VVV seems somewhat similar to ours at least when compared to Flywheel and WP Engine. Have not tested the dev environment from 10up. Some differences based on brief testing:
config.yml
options. Maybe we should look into some of those options more deeply?
---
#
#
#
sites:
wordpress-one: skip_provisioning: false description: "A standard WP install, useful for building plugins, testing things, etc" repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git hosts:
one.wordpress.test
wordpress-two: skip_provisioning: false description: "A standard WP install, useful for building plugins, testing things, etc" repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git hosts:
two.wordpress.test
wordpress-trunk: skip_provisioning: true # provisioning this one takes longer, so it's disabled by default description: "An svn based WP Core trunk dev setup, useful for contributor days, Trac tickets, patches" repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop.git hosts:
trunk.wordpress.test
wordpress-meta-environment: skip_provisioning: true # disabled by default, this takes a long time to provision repo: https://github.com/WordPress/meta-environment.git
utilities: core: # The core VVV utility
vm_config:
memory: 2048
cores: 2
vagrant up
general:
db_backup: true
db_restore: true
Maybe we should direct some effort to support multisite configuration into config.yml
with the aid of https://github.com/Seravo/wordpress/issues/81? I don't think that we can directly compare VVV with our Vagrant environment, because ours is only intended for serving a single site, whereas VVV seems to have support for subdomain installations for multiple sites (wordpress-one
, wordpress-two
etc).
Does @ottok have anything to comment about the results above, or can this issue be closed? I also have created a shared Google docs document comparing also to other local environments, but not linking it here due to this being a public repo.
Other alternatives to compare to:
Docksal Command line based, wp-cli support docksal.io
Vagrant Command line based. Has a WP focused conf. vagrantup.com
Local by Flywheel GUI, SSL localwp.com
DesktopServer GUI, SSL serverpress.com
These are based on directly on docker-compose, but on a custom cli tool that creates the different files and environments, including docker-compose files: https://10up.github.io/wp-local-docker-docs/, https://lando.dev/
Compare our Seravo Vagrant box to the develop branch of the official WordPress Vagrant box: https://github.com/Varying-Vagrant-Vagrants/VVV
If there are any developer tools, speed optimizations etc cool things, consider copying them over to our image. Note however to keep the PHP/Nginx part in parity with our production environment, there should be no surprises when developers push their sites to production.