If you encounter any errors when following these instructions, please check the troubleshooting section for known issues.
- Ubuntu (18.04 tested) users can install everything just by pasting this command into a terminal:
sudo apt install vagrant libvirt-daemon-system nfs-kernel-server -y && vagrant plugin install vagrant-libvirt
Create a new folder which will contain all your future projects.
We will use ~/Projects in these instructions, adapt the instructions as needed if you choose a different path.
Save the Vagrantfile in your new folder.
The file must be saved with the same Vagrantfile name. Mac OS X seems to like adding a .txt extension when saving. See the troubleshooting section below for instructions on renaming the file.
- Vagrant up in this directory:
cd ~/Projects/ && vagrant up
Navigate to localhost:8080.
If everything is working correctly, you should see the UWDE home page. Simply follow the instructions to install a version of WordPress and setup your projects repository.
When you want to start the program in future, just run this command again:
cd ~/Projects && vagrant up
If you want to stop the program, just run:
cd ~/Projects && vagrant halt
sudo: unable to resolve host ubuntu-xenial mesg: ttyname failed: Inappropriate ioctl for device
This is fixed in later versions of Vagrant. Ensure you are running version >=1.8.4.
A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target machine from `vagrant global-status` to run this command on. A final option is to change to a directory with a Vagrantfile and to try again.
Ensure your vagrant file is named exactly Vagrantfile. Mac OS X has a tendency to add .txt to the file which will not work. Rename it:
mv Vagrantfile.txt Vagrantfile
The box 'bento/ubuntu-16.04' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/bento/ubuntu-16.04"]
This seems to be an issue on some versions of Vagrant. Please ensure you are running version >=1.8.8.
Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate with the guest machine within the configured ("config.vm.boot_timeout" value) time period.
This may be an issue on VirtualBox. Please ensure you are running the latest version of VirtualBox. After updating Virtualbox, you may need to run vagrant destroy before running vagrant up again.