Sha256: 337b6fa6e3c75fb7d53334d1102156fea894fce45df818a32dc0bfec4a26fcb2
Contents?: true
Size: 888 Bytes
Versions: 5
Compression:
Stored size: 888 Bytes
Contents
--- page_title: "Custom Provider - Vagrant Share" sidebar_current: "share-provider" --- # Custom Provider <div class="alert alert-warn"> <p> <strong>Warning: Advanced Topic!</strong> This topic is related to developing Vagrant plugins. If you're not interested in this or you're just starting with Vagrant, it is safe to skip this page. </p> </div> If you're developing a [custom provider](/v2/plugins/providers.html), you'll 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 can't detect an address, return `nil`.
Version data entries
5 entries across 2 versions & 2 rubygems