Sha256: 626691ee3fe087de2f4555e51efe06471319df5807ab58b665d7c073dd93b38c
Contents?: true
Size: 1.05 KB
Versions: 19
Compression:
Stored size: 1.05 KB
Contents
--- layout: "docs" page_title: "Custom Provider - Vagrant Share" sidebar_current: "share-provider" description: |- If you are developing a custom Vagrant provider, you will need to do a tiny bit more work in order for it to work well with Vagrant Share. --- # Custom Provider <div class="alert alert-warning"> <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. </div> If you are developing a [custom Vagrant provider](/docs/plugins/providers.html), you will need to do a tiny bit more work in order for it to work well with Vagrant Share. For now, this is only one step: * `public_address` 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 `nil`.
Version data entries
19 entries across 15 versions & 4 rubygems