From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Thu, 14 Aug 2025 22:58:58 -0500
Subject: removing all downloaded devdocs files

---
 devdocs/vagrant/cli%2Fprovision.html | 7 -------
 1 file changed, 7 deletions(-)
 delete mode 100644 devdocs/vagrant/cli%2Fprovision.html

(limited to 'devdocs/vagrant/cli%2Fprovision.html')

diff --git a/devdocs/vagrant/cli%2Fprovision.html b/devdocs/vagrant/cli%2Fprovision.html
deleted file mode 100644
index 30089253..00000000
--- a/devdocs/vagrant/cli%2Fprovision.html
+++ /dev/null
@@ -1,7 +0,0 @@
-<h1 id="provision">  Provision </h1> <p><strong>Command: <code>vagrant provision [vm-name]</code></strong></p> <p>Runs any configured <a href="../provisioning/index">provisioners</a> against the running Vagrant managed machine.</p> <p>This command is a great way to quickly test any provisioners, and is especially useful for incremental development of shell scripts, Chef cookbooks, or Puppet modules. You can just make simple modifications to the provisioning scripts on your machine, run a <code>vagrant provision</code>, and check for the desired results. Rinse and repeat.</p> <h1 id="options">  Options </h1> <ul> <li>
-<a href="#provision-with-x-y-z"><code>--provision-with x,y,z</code></a> - This will only run the given provisioners. For example, if you have a <code>:shell</code> and <code>:chef_solo</code> provisioner and run <code>vagrant provision --provision-with shell</code>, only the shell provisioner will be run. </li> </ul><div class="_attribution">
-  <p class="_attribution-p">
-    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
-    <a href="https://www.vagrantup.com/docs/cli/provision.html" class="_attribution-link">https://www.vagrantup.com/docs/cli/provision.html</a>
-  </p>
-</div>
-- 
cgit v1.2.3