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

---
 .../vagrant/vagrantfile%2Fmachine_settings.html    | 31 ++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 devdocs/vagrant/vagrantfile%2Fmachine_settings.html

(limited to 'devdocs/vagrant/vagrantfile%2Fmachine_settings.html')

diff --git a/devdocs/vagrant/vagrantfile%2Fmachine_settings.html b/devdocs/vagrant/vagrantfile%2Fmachine_settings.html
new file mode 100644
index 00000000..0a9082dc
--- /dev/null
+++ b/devdocs/vagrant/vagrantfile%2Fmachine_settings.html
@@ -0,0 +1,31 @@
+<h1 id="machine-settings">  Machine Settings </h1> <p><strong>Config namespace: <code>config.vm</code></strong></p> <p>The settings within <code>config.vm</code> modify the configuration of the machine that Vagrant manages.</p> <h2 id="available-settings">  Available Settings </h2> <ul> <li>
+<p><a href="#config-vm-base_mac" id="config-vm-base_mac"><code>config.vm.base_mac</code></a> (string) - The MAC address to be assigned to the default NAT interface on the guest. <em>Support for this option is provider dependent.</em></p> </li> <li>
+<p><a href="#config-vm-base_address"><code>config.vm.base_address</code></a> (string) - The IP address to be assigned to the default NAT interface on the guest. <em>Support for this option is provider dependent.</em></p> </li> <li>
+<p><a href="#config-vm-boot_timeout"><code>config.vm.boot_timeout</code></a> (integer) - The time in seconds that Vagrant will wait for the machine to boot and be accessible. By default this is 300 seconds.</p> </li> <li>
+<p><a href="#config-vm-box"><code>config.vm.box</code></a> (string) - This configures what <a href="../boxes">box</a> the machine will be brought up against. The value here should be the name of an installed box or a shorthand name of a box in <a href="https://www.vagrantup.com/docs/vagrant-cloud">HashiCorp's Vagrant Cloud</a>.</p> </li> <li>
+<p><a href="#config-vm-box_check_update"><code>config.vm.box_check_update</code></a> (boolean) - If true, Vagrant will check for updates to the configured box on every <code>vagrant up</code>. If an update is found, Vagrant will tell the user. By default this is true. Updates will only be checked for boxes that properly support updates (boxes from <a href="https://www.vagrantup.com/docs/vagrant-cloud">HashiCorp's Vagrant Cloud</a> or some other versioned box).</p> </li> <li>
+<p><a href="#config-vm-box_download_checksum"><code>config.vm.box_download_checksum</code></a> (string) - The checksum of the box specified by <code>config.vm.box_url</code>. If not specified, no checksum comparison will be done. If specified, Vagrant will compare the checksum of the downloaded box to this value and error if they do not match. Checksum checking is only done when Vagrant must download the box. If this is specified, then <code>config.vm.box_download_checksum_type</code> must also be specified.</p> </li> <li>
+<p><a href="#config-vm-box_download_checksum_type"><code>config.vm.box_download_checksum_type</code></a> (string) - The type of checksum specified by <code>config.vm.box_download_checksum</code> (if any). Supported values are currently "md5", "sha1", and "sha256".</p> </li> <li>
+<p><a href="#config-vm-box_download_client_cert"><code>config.vm.box_download_client_cert</code></a> (string) - Path to a client certificate to use when downloading the box, if it is necessary. By default, no client certificate is used to download the box.</p> </li> <li>
+<p><a href="#config-vm-box_download_ca_cert"><code>config.vm.box_download_ca_cert</code></a> (string) - Path to a CA cert bundle to use when downloading a box directly. By default, Vagrant will use the Mozilla CA cert bundle.</p> </li> <li>
+<p><a href="#config-vm-box_download_ca_path"><code>config.vm.box_download_ca_path</code></a> (string) - Path to a directory containing CA certificates for downloading a box directly. By default, Vagrant will use the Mozilla CA cert bundle.</p> </li> <li>
+<p><a href="#config-vm-box_download_insecure"><code>config.vm.box_download_insecure</code></a> (boolean) - If true, then SSL certificates from the server will not be verified. By default, if the URL is an HTTPS URL, then SSL certs will be verified.</p> </li> <li>
+<p><a href="#config-vm-box_download_location_trusted"><code>config.vm.box_download_location_trusted</code></a> (boolean) - If true, then all HTTP redirects will be treated as trusted. That means credentials used for initial URL will be used for all subsequent redirects. By default, redirect locations are untrusted so credentials (if specified) used only for initial HTTP request.</p> </li> <li>
+<p><a href="#config-vm-box_url"><code>config.vm.box_url</code></a> (string, array of strings) - The URL that the configured box can be found at. If <code>config.vm.box</code> is a shorthand to a box in <a href="https://www.vagrantup.com/docs/vagrant-cloud">HashiCorp's Vagrant Cloud</a> then this value does not need to be specified. Otherwise, it should point to the proper place where the box can be found if it is not installed. This can also be an array of multiple URLs. The URLs will be tried in order.</p> <p>Note that any client certificates, insecure download settings, and so on will apply to all URLs in this list. The URLs can also be local files by using the <code>file://</code> scheme. For example: "file:///tmp/test.box".</p> </li> <li>
+<p><a href="#config-vm-box_version"><code>config.vm.box_version</code></a> (string) - The version of the box to use. This defaults to "&gt;= 0" (the latest version available). This can contain an arbitrary list of constraints, separated by commas, such as: <code>&gt;= 1.0, &lt; 1.5</code>. When constraints are given, Vagrant will use the latest available box satisfying these constraints.</p> </li> <li>
+<p><a href="#config-vm-communicator"><code>config.vm.communicator</code></a> (string) - The communicator type to use to connect to the guest box. By default this is <code>"ssh"</code>, but should be changed to <code>"winrm"</code> for Windows guests.</p> </li> <li>
+<p><a href="#config-vm-graceful_halt_timeout"><code>config.vm.graceful_halt_timeout</code></a> (integer) - The time in seconds that Vagrant will wait for the machine to gracefully halt when <code>vagrant halt</code> is called. Defaults to 60 seconds.</p> </li> <li>
+<p><a href="#config-vm-guest"><code>config.vm.guest</code></a> (string, symbol) - The guest OS that will be running within this machine. This defaults to <code>:linux</code>, and Vagrant will auto-detect the proper distro. However, this should be changed to <code>:windows</code> for Windows guests. Vagrant needs to know this information to perform some guest OS-specific things such as mounting folders and configuring networks.</p> </li> <li>
+<p><a href="#config-vm-hostname"><code>config.vm.hostname</code></a> (string) - The hostname the machine should have. Defaults to nil. If nil, Vagrant will not manage the hostname. If set to a string, the hostname will be set on boot. If set, Vagrant will update <code>/etc/hosts</code> on the guest with the configured hostname.</p> </li> <li>
+<p><a href="#config-vm-ignore_box_vagrantfile"><code>config.vm.ignore_box_vagrantfile</code></a> (boolean) - If true, Vagrant will not load the the settings found inside a boxes Vagrantfile, if present. Defaults to <code>false</code>.</p> </li> <li>
+<p><a href="#config-vm-network"><code>config.vm.network</code></a> - Configures <a href="../networking/index">networks</a> on the machine. Please see the networking page for more information.</p> </li> <li>
+<p><a href="#config-vm-post_up_message"><code>config.vm.post_up_message</code></a> (string) - A message to show after <code>vagrant up</code>. This will be shown to the user and is useful for containing instructions such as how to access various components of the development environment.</p> </li> <li>
+<p><a href="#config-vm-provider"><code>config.vm.provider</code></a> - Configures <a href="../providers/configuration">provider-specific configuration</a>, which is used to modify settings which are specific to a certain <a href="../providers/index">provider</a>. If the provider you are configuring does not exist or is not setup on the system of the person who runs <code>vagrant up</code>, Vagrant will ignore this configuration block. This allows a Vagrantfile that is configured for many providers to be shared among a group of people who may not have all the same providers installed.</p> </li> <li>
+<p><a href="#config-vm-provision"><code>config.vm.provision</code></a> - Configures <a href="../provisioning/index">provisioners</a> on the machine, so that software can be automatically installed and configured when the machine is created. Please see the page on provisioners for more information on how this setting works.</p> </li> <li>
+<p><a href="#config-vm-synced_folder"><code>config.vm.synced_folder</code></a> - Configures <a href="../synced-folders/index">synced folders</a> on the machine, so that folders on your host machine can be synced to and from the guest machine. Please see the page on synced folders for more information on how this setting works.</p> </li> <li>
+<p><a href="#config-vm-usable_port_range"><code>config.vm.usable_port_range</code></a> (range) - A range of ports Vagrant can use for handling port collisions and such. Defaults to <code>2200..2250</code>.</p> </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/vagrantfile/machine_settings.html" class="_attribution-link">https://www.vagrantup.com/docs/vagrantfile/machine_settings.html</a>
+  </p>
+</div>
-- 
cgit v1.2.3