2016-01-19 18:08:53 +00:00
|
|
|
---
|
|
|
|
layout: "docs"
|
|
|
|
page_title: "Custom Provider - Vagrant Share"
|
|
|
|
sidebar_current: "share-provider"
|
|
|
|
description: |-
|
2016-01-19 19:54:13 +00:00
|
|
|
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.
|
2016-01-19 18:08:53 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
# Custom Provider
|
|
|
|
|
|
|
|
<div class="alert alert-warning">
|
2016-01-19 19:54:13 +00:00
|
|
|
<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.
|
2016-01-19 18:08:53 +00:00
|
|
|
</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
|
2016-01-19 19:54:13 +00:00
|
|
|
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`.
|