This repository has been archived by the owner on Mar 6, 2021. It is now read-only.
Adds yaml option for private or public network interface #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new yaml configuration option called
network
which allows you to choose between the vagrantprivate
andpublic
network interfaces.Please note that the yaml will fall back to
private
if any other value is used.Why
Using a public vagrant network allows you to expose your box over your (local) network which is extremely useful for situations where testing from your workstation alone just won't cut it (e.g. when developing mobile applications).
A real world use case would be testing your mobile application from a non-broken iPhone.:
public
vagrant networkcakebox.yourdomain.com
pointing to the ip-address of your box (e.g.192.168.1.10
)cakebox.yourdomain.com
How
cd cakebox
git pull
Cakebox.yaml
vagrant reload