So basically localtunnel (http://progrium.com/localtunnel/), but integrated into Vagrant? Plus some SSH magic.
Vagrant Share
21–30 of 47 posts
Re: Vagrant Share
#22I helped build something like this for developing Facebook apps. I'm happy to see that the service is still running at https://tunnlr.com/. It's a good tool, and I think it makes sense as a Vagrant plugin but I'm surprised this is becoming part of core.
Re: Vagrant Share
#23This is exactly why widespread adoption of IPv6 would make everyone more productive. Why doesn't every Vagrant box have an IPv6 address that you can expose by opening up firewall rules? Well, aside from ISP's being slow and developers not spending the 40 minutes necessary to set IPA tunnel, VirtualBox does not support IPv6 addresses on bridged interfaces if the host interface is a wireless card. Sad day all around.
Edit: in fact I wonder if instead of building yet another IPv4 traversal tool, new applications that require P2P connectivity should actually start building it as an IPv6-in-something tunnel. There are plenty of ways to do this including AYIYA which while not fantastic would actually work really well here.
Re: Vagrant Share
#24There are lots of vagrants, you don't have to share, everyone can have one or two all of their own. But if you choose to share I'm sure this is the best way.
Hopefully they expand in to Hobo's, Bums, and the underemployed.
Re: Vagrant Share
#25I noticed the share funcionality uses a Vagrant URL (vagrantshare.com). Sure enough, when I scrolled to the bottom there was mention of a web service. I imagine this web service will be monitized as it just makes a lot of sense, but hoping that single devs can still demo their projects to friends without having to pay a fee. If my above assumption is true, would a Vagrant Share Enteprise be in the works/future, simil…
It's most likely being used to generate a nice URL that does dynamic DNS forwarding to the actual server.
One could probably get away with just using an IP and a port, but within an organization that's behind a firewall it's not always immediately obvious which IP and port to use.
Re: Vagrant Share
#26Will this also be open source so I can run my own proxy?
Re: Vagrant Share
#27Feature request for the Mac OS Vagrant port: please don't copy your executable into /usr/bin when running the installer (and that seems to be the only reason the installer exists at all — it would be better distributed just as a .zip containing the Vagrant directory; I can take it from there). /usr/bin is for system-provided executables, not for applications. I understand the wish to provide an easily-accessible comm…
We used to do that, but we received SO MANY complaints that it wasn't instantly available on the PATH, that we symlinked into /usr/bin. An alternate approach: Mac has some way to hook into shell profile loading so we should be able to inject a script somewhere that amends the PATH. This turns out to be a little crazy on Mac for some reason I don't remember, but should be possible. Surprisingly, things are better here…
On Windows you could probably just set an entry in App Paths. No need to modify the PATH environment variable at all.
Re: Vagrant Share
#28So basically localtunnel ( http://progrium.com/localtunnel/ ), but integrated into Vagrant? Plus some SSH magic.
https://localtunnel.me/ does the same thing but with ssl for free.
Likely the first to market was http://showoff.io ( pivoted to https://forwardhq.com/ ), promoted by http://pow.cx
Re: Vagrant Share
#29Earlier quoted context omitted.
So they can only get their job done if they are in the same timezone or if you don't happen to reboot your laptop? Those don't seem like great use cases. Plus if you are at the point of QA/PM review of what you've done, the code has already been checked into source control. They could just as easily spin up their own VM with the Vagrantfile.
You are vastly overestimating the technical abilities of the average QA person. "Just as easily spinning up their own VM with the Vagrantfile" assumes a significant base understanding of a lot of technologies.
I think you are vastly underestimating their abilities. You install git, virtual box, and vagrant. Clone the repo and type vagrant up. If they've never done it they can refer to the wiki page you typed up for everybody. I know every QA person at my workplace could easily do it.
Re: Vagrant Share
#30Just the other day I was telling a friend of mine how having the ability to share my Vagrant dev environment was the only missing from what I would consider my dream development workflow. Edit: I got so excited I even forgot to thank Mitchell for all the hard work. Vagrant completely changed my (work) life. Thank you a thousand times, Mitchell!
How would you use this? I'm racking my brain trying to figure out what this would be used for. I just shared my vagrant file.
We use ngrok (vagrant share alternative-ish) to test integration with third-party services that have to send requests to our system. Works great.