diff options
Diffstat (limited to 'devdocs/vagrant/share%2Fprovider.html')
| -rw-r--r-- | devdocs/vagrant/share%2Fprovider.html | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/devdocs/vagrant/share%2Fprovider.html b/devdocs/vagrant/share%2Fprovider.html new file mode 100644 index 00000000..d4c491d0 --- /dev/null +++ b/devdocs/vagrant/share%2Fprovider.html @@ -0,0 +1,8 @@ +<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"> + © 2010–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> |
