vagrant/plugins
Mitchell Hashimoto 76e29b912f providers/docker: lower priority
We do this mostly because Docker is the only provider that using it
requires some amount of Docker-specific knowledge. VirtualBox, VMware,
etc. kind of "just work". It is not the likely case that someone does
a `vagrant up` and expects Docker, at this point.
2014-05-01 09:51:50 -07:00
..
commands commands/init: force flag [GH-3564] 2014-04-28 20:22:09 -07:00
communicators Use new Ruby hash initializer syntax 2014-04-26 21:07:26 -07:00
guests Display deprecation warning for unused halt config properties 2014-05-01 09:03:49 -07:00
hosts hosts/darwin: use a temp dir since Tempfile is deleted right away 2014-04-21 13:56:43 -07:00
kernel_v1 Handle a lot of TODOs 2014-04-29 16:50:58 -07:00
kernel_v2 kernel/v2: make sure communicator is a symbol 2014-04-21 13:56:41 -07:00
providers providers/docker: lower priority 2014-05-01 09:51:50 -07:00
provisioners Fix remote/downloaded shell scripts 2014-04-30 19:39:37 -07:00
synced_folders synced_folders/rsync: fix oddness on Windows 2014-04-28 14:49:33 -07:00
README.md Add README to plugin directory 2012-04-18 17:48:06 -07:00

README.md

Vagrant Core Plugins

These are plugins that ship with Vagrant. Vagrant core uses its own plugin system to power a lot of the core pieces that ship with Vagrant. Each plugin will have its own README which explains its specific role.