Skip to content
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

Merged
merged 1 commit into from
Jan 7, 2017

Conversation

bravo-kernel
Copy link
Contributor

@bravo-kernel bravo-kernel commented Jan 7, 2017

This PR introduces a new yaml configuration option called network which allows you to choose between the vagrant private and public 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.:

  1. Configure your yaml to use the public vagrant network
  2. Create a public DNS record cakebox.yourdomain.com pointing to the ip-address of your box (e.g. 192.168.1.10)
  3. Open your iPhone and browse to cakebox.yourdomain.com

How

  1. cd cakebox
  2. git pull
  3. update your Cakebox.yaml
  4. vagrant reload

@bravo-kernel bravo-kernel merged commit 4d531cd into dev Jan 7, 2017
@bravo-kernel bravo-kernel deleted the network-option branch January 7, 2017 11:34
@bravo-kernel bravo-kernel changed the title Adds yaml option for private or public network Adds yaml option for private or public network interface Jan 7, 2017
@bravo-kernel bravo-kernel mentioned this pull request Mar 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant