The problem: You code your mobile web apps on your desktop, and it’s hard to see the changes.
Until OS X Mavericks kills the feature, you used to be able to daisy chain your local WiFi off your ethernet connection, and serve your local environment to your mobile devices via WiFi. It was a sad day when they killed it. It made development so easy. I couldn’t find any other alternative that didn’t involve time consuming network hacks. The XIP service got me close, but it was unreliable when I was at a location with high network security.
All was hopeless until I found Vagrant Share.
Now this is my workflow.
- I code.
- I save.
- My local browser refreshes. My iPhone refreshes.
Vagrant Share allows you to share your Vagrant environment with anyone in the world, enabling collaboration directly in your Vagrant environment in almost any network environment with just a single command:
Vagrant share has three primary modes or features:
HTTP sharing will create a URL that you can give to anyone. This URL will route directly into your Vagrant environment. The person using this URL does not need Vagrant installed, so it can be shared with anyone. This is useful for testing webhooks or showing your work to clients, teammates, managers, etc.
SSH sharing will allow instant SSH access to your Vagrant environment by anyone by running
vagrant connect --sshon the remote side. This is useful for pair programming, debugging ops problems, etc.
General sharing allows anyone to access any exposed port of your Vagrant environment by running
vagrant connecton the remote side. This is useful if the remote side wants to access your Vagrant environment as if it were a computer on the LAN.
The quick & dirty install.
I highly encourage you to head over to the vagrant site and check out their docs. They’re pretty detailed and it’s important to get a solid grip on what’s going on. That said, if you plug this into your machine, you’ll probably be alright.
$ mkdir vagrant_getting_started