wp-vagrant
wp-vagrant copied to clipboard
Seravo
Vagrant box for the Seravo WordPress project template
While booting up the latest v20201205.0.0 box, I saw this: ``` ==> wordpress-box: Checking for guest additions in VM... wordpress-box: The guest additions on this VM do not match the...
Output from `vagrant up` after upgrading to VirtualBox >= 6.1.28: ``` ▶ vagrant up Bringing machine 'wordpress-box' up with 'virtualbox' provider... ==> wordpress-box: Importing base box 'seravo/wordpress-beta'... ==> wordpress-box: Matching...
If one runs `vagrant up` for an existing project after `vagrant box update` was run, one will not be able to access the box anymore due to mismatch in SSH...
This requires extensive testing before merged and rolled out.
After running wp-pull-production-db all wp-cli commands stop working, because the database has now the production Network domain while the Vagrant config files refer to the local version. The temporary workaround...
XDebug is a bit slow and some users would like to have it disabled by default. However the pretty stack traces it makes is nice. One alternative would be to...
Does currently not work since the Docker image itself is not self-contained enough and still needs `sc` to start it. But some day we could publish `docker` as a native...
Steps for current demo: ``` # Assuming original box name is seravo/wordpress-beta version 0 qemu-img convert -f vmdk -O qcow2 ~/.vagrant.d/boxes/seravo-VAGRANTSLASH-wordpress-beta/0/virtualbox/*.vmdk seravo-wordpress-beta.img /usr/share/doc/vagrant-libvirt/examples/create_box.sh seravo-wordpress-beta.img vagrant box add seravo-wordpress-beta.box --name seravo/wordpress-beta...
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...