provide DNS for local dev
We currently suggest adding an entry in
aegir.vm and some example URLs. However, we now own http://aegir.dev. I think we might want to point
192.168.0.201, so that we get automatic resolution into the Vagrant VM. Of course, that won't work if you deploy to a cloud host, and such. But we can keep the
/etc/hosts suggestion for such use-cases.
I wonder whether that's the best IP to use though... maybe
10 might be better, since we can better avoid collisions.
I've also set this up where I change the Vagrantfile to make the network "public". This allow me to, for example, access an Aegir5 VM running on my desktop, from my laptop, over my local wifi LAN, which can be handy. I think the IP then needs to be in the default subnet that clients are using on the local wifi, which is usually 192.168.0.1/24. So the current IP address should still work in that case.
My point here is to minimize the effort for the majority of users/devs, while still allowing those with unusual setups to easily adjust. So, maybe we should add an FAQ or troubleshooting section to the dev docs.
While the local dev setup is currently only useful for developing Aegir5 itself, I think the Valkyrie model could still be viable. That is, we could make a local install work as a local client in a "local-dev -> local-QA -> shared-staging -> public-prod" kind of system; as well as supporting other local-dev tools, like Lando.
But it provides us an opportunity to build a GUI for local dev, which makes it somewhat comparable to Acquia's dev-desktop or Kalabox (I think).