Notes.md

• need the internal network to check code out / run composer at least - no way around this

• very slow on non ssd macs - Ignacio has a newer machine so is low on the list for SSD upgrades, but vagrant is still slow.

• Admin access seems to be required - issues when people run on an AD account. If we are going to run vagrant, we need to let people know the best way is to run vagrant in an admin non AD account

• NFS still proving problematic - firewall rules possibly not quite working, but difficult to test. Running the required rule as admin did seem to work.

• if we dont have shared folders from host, code checkouts not persistent after doing vagrant destroy

• Jordis laptop is 32bit - I swear i've run it on a windows laptop, we must have some 32bit and some 64bit

• nscd issue with resolv.conf - after provisioning it run nscd restart to prevent this

• resolv.conf is getting overwritten - may be to do with vagrant halt. All our services rely on the correct resolv.conf being present. Solution is to either provision using mock services and a hosts file, which we would need to do for external people anyway, or to make sure people know to run vagrant provision if issues connecting to db etc. Vagrant suspend may also solve this

• will has a weird issue with port forwarding which we need to debug further, no one else has seen this