The docs mention several Vagrant plugins, most of which are not necessary. Identify unnecessary plugins and remove them from the Vagrantfile and the docs. If any plugins are required or recommended, list them as such in develop.md.
For example, the Vagrantfile includes this line:
staging.hostmanager.aliases = %w(securedrop-monitor-server-alias)
The Ansible config already handles writing to /etc/hosts, so the vagrant-hostmanager plugin isn't useful. Since mention of the plugin is buried down at the bottom of develop.md, trying to run the VMs on a pristine clone of the git repo will cause failure if the user doesn't have the plugin installed locally. This is a frustration for new contributors.
vagrant-cachier was disabled half a year ago (8745bd8) and nothing has changed that would allow us to re-enable it, so get rid of it.
The vagrant-digitalocean plugin is useful but should not be required. Make sure it's not required before moving it to a Recommended section. Consider recommending vagrant-vbox-snapshot as well.
The docs mention several Vagrant plugins, most of which are not necessary. Identify unnecessary plugins and remove them from the Vagrantfile and the docs. If any plugins are required or recommended, list them as such in
develop.md.For example, the
Vagrantfileincludes this line:staging.hostmanager.aliases = %w(securedrop-monitor-server-alias)The Ansible config already handles writing to
/etc/hosts, so thevagrant-hostmanagerplugin isn't useful. Since mention of the plugin is buried down at the bottom ofdevelop.md, trying to run the VMs on a pristine clone of the git repo will cause failure if the user doesn't have the plugin installed locally. This is a frustration for new contributors.vagrant-cachierwas disabled half a year ago (8745bd8) and nothing has changed that would allow us to re-enable it, so get rid of it.The
vagrant-digitaloceanplugin is useful but should not be required. Make sure it's not required before moving it to a Recommended section. Consider recommendingvagrant-vbox-snapshotas well.