From 509872e91b4aa52dd92b372273566efd5c10b22f Mon Sep 17 00:00:00 2001 From: Fabio Rehm Date: Wed, 5 Feb 2014 20:48:42 -0200 Subject: [PATCH] Forgot to update this to reflect whats going on under the hood --- docs/how-does-it-work.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/how-does-it-work.md b/docs/how-does-it-work.md index 80a8f5d..b357d89 100644 --- a/docs/how-does-it-work.md +++ b/docs/how-does-it-work.md @@ -20,12 +20,11 @@ _as part of_ the boot process (synced folders are actually `lxc-start` parameter and as of now we are not able to get some information that this plugin requires about the guest machine / container before it is actually up and running. -Under the hood, the plugin will monkey patch `Vagrant::Builtin::Provision` and -will set things up for each configured cache bucket _before and after_ running each -defined provisioner. Before halting the machine, it will also revert the changes -required to set things up by hooking into calls to `Vagrant::Builtin::GracefulHalt` -so that you can repackage the machine for others to use without requiring users to -install the plugin as well. +Under the hood, the plugin will hook into Vagrant in order to set things up for each +configured cache bucket _before and after_ running each defined provisioner. Before +halting the machine, it will also revert the changes required to set things up by +hooking into calls to `Vagrant::Builtin::GracefulHalt` so that you can repackage +the machine for others to use without requiring users to install the plugin as well. Please keep in mind that this plugin won't do magic, if you are compiling things during provisioning or manually downloading packages outside of a bucket you