From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Sun, 7 Apr 2024 13:41:34 -0500
Subject: new repository

---
 devdocs/vagrant/provisioning%2Findex.html | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 devdocs/vagrant/provisioning%2Findex.html

(limited to 'devdocs/vagrant/provisioning%2Findex.html')

diff --git a/devdocs/vagrant/provisioning%2Findex.html b/devdocs/vagrant/provisioning%2Findex.html
new file mode 100644
index 00000000..8dbec953
--- /dev/null
+++ b/devdocs/vagrant/provisioning%2Findex.html
@@ -0,0 +1,9 @@
+<h1 id="provisioning">  Provisioning </h1> <p>Provisioners in Vagrant allow you to automatically install software, alter configurations, and more on the machine as part of the <code>vagrant up</code> process.</p> <p>This is useful since <a href="../boxes">boxes</a> typically are not built <em>perfectly</em> for your use case. Of course, if you want to just use <code>vagrant ssh</code> and install the software by hand, that works. But by using the provisioning systems built-in to Vagrant, it automates the process so that it is repeatable. Most importantly, it requires no human interaction, so you can <code>vagrant destroy</code> and <code>vagrant up</code> and have a fully ready-to-go work environment with a single command. Powerful.</p> <p>Vagrant gives you multiple options for provisioning the machine, from simple shell scripts to more complex, industry-standard configuration management systems.</p> <p>If you've never used a configuration management system before, it is recommended you start with basic <a href="shell">shell scripts</a> for provisioning.</p> <p>You can find the full list of built-in provisioners and usage of these provisioners in the navigational area to the left.</p> <h2 id="when-provisioning-happens">  When Provisioning Happens </h2> <p>Provisioning happens at certain points during the lifetime of your Vagrant environment:</p> <ul> <li>
+<p>On the first <code>vagrant up</code> that creates the environment, provisioning is run. If the environment was already created and the up is just resuming a machine or booting it up, they will not run unless the <code>--provision</code> flag is explicitly provided.</p> </li> <li>
+<p>When <code>vagrant provision</code> is used on a running environment.</p> </li> <li>
+<p>When <code>vagrant reload --provision</code> is called. The <code>--provision</code> flag must be present to force provisioning.</p> </li> </ul> <p>You can also bring up your environment and explicitly <em>not</em> run provisioners by specifying <code>--no-provision</code>.</p><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/provisioning/" class="_attribution-link">https://www.vagrantup.com/docs/provisioning/</a>
+  </p>
+</div>
-- 
cgit v1.2.3