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/share%2Fprovider.html | 8 --------
 1 file changed, 8 deletions(-)
 delete mode 100644 devdocs/vagrant/share%2Fprovider.html

(limited to 'devdocs/vagrant/share%2Fprovider.html')

diff --git a/devdocs/vagrant/share%2Fprovider.html b/devdocs/vagrant/share%2Fprovider.html
deleted file mode 100644
index d4c491d0..00000000
--- a/devdocs/vagrant/share%2Fprovider.html
+++ /dev/null
@@ -1,8 +0,0 @@
-<h1 id="custom-provider">  Custom Provider </h1> <blockquote class="alert alert-warning"> <p><strong>Warning: Advanced Topic!</strong> This topic is related to developing Vagrant plugins. If you are not interested in this or you are just starting with Vagrant, it is safe to skip this page.</p> </blockquote>
-<p>If you are developing a <a href="../plugins/providers">custom Vagrant provider</a>, you will need to do a tiny bit more work in order for it to work well with Vagrant Share.</p> <p>For now, this is only one step:</p> <ul> <li>
-<a href="#public_address"><code>public_address</code></a> provider capability - You must implement this capability to return a string that is an address that can be used to access the guest from Vagrant. This does not need to be a globally routable address, it only needs to be accessible from the machine running Vagrant. If you cannot detect an address, return <code>nil</code>. </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/share/provider.html" class="_attribution-link">https://www.vagrantup.com/docs/share/provider.html</a>
-  </p>
-</div>
-- 
cgit v1.2.3