I've been using this for a while and have really been enjoying it. Also handy being able to choose between a few geographical locations, to reduce latency which is always really bad from Australia to elsewhere.
Nitrous.io brings its browser-based app development environment into public beta
21–25 of 25 posts
Re: Nitrous.io brings its browser-based app development environment into public beta
#22I really dig the concept. Having seen the downsides of vagrant on a few projects, I'm definitely interested in the feasability of cloud-hosted dev environments. Virtualization on top of cloud servers could make this cheaper than running your own, and if you got clever you could probably setup shared services for SOA heavy architectures.
I just recently started using Vagrant. What downsides have you seen? Any show-stoppers?
It would be very interesting to see some sort of provisioning system built into Nitrous, much like using saltstack/chef/puppet with Vagrant.
Re: Nitrous.io brings its browser-based app development environment into public beta
#23Awesome. I'm looking to learn some nodejs, and this will spare me from getting my head wrapped around how to handle the environment.
Re: Nitrous.io brings its browser-based app development environment into public beta
#24I really dig the concept. Having seen the downsides of vagrant on a few projects, I'm definitely interested in the feasability of cloud-hosted dev environments. Virtualization on top of cloud servers could make this cheaper than running your own, and if you got clever you could probably setup shared services for SOA heavy architectures.
I just recently started using Vagrant. What downsides have you seen? Any show-stoppers? It would be very interesting to see some sort of provisioning system built into Nitrous, much like using saltstack/chef/puppet with Vagrant.
I'm also curious about the downsides of using Vagrant.
Correct me if I'm wrong but if you have full access to the command line you can probably get your recipes working there. If this works, I understand it's not as easy as provisioning with Vagrant but it's a workaround for now.
Re: Nitrous.io brings its browser-based app development environment into public beta
#25Help me understand. Why do I want to move my development to the cloud? I grok a Heroku competitor, but I'm really having a hard time understanding what I could possibly gain from developing in the cloud?
Also in case you have dev-environment setup on multiple computers, it eliminates the need to keep them in sync.
Also good for hobby projects where you just want to try out a technology without spending time on setting up the environment