Has anyone had much luck using Chef solo to provision their Vagrant box AND their production/staging environments? I'm currently attempting this, and it has been kind of a pain in the ass. Chef-solo seems woefully underpowered.
Vagrant: Create and configure portable development environments
31–40 of 80 posts
Re: Vagrant: Create and configure portable development environments
#32If you love vagrant, be sure to give the plugin 'Sahara' a try. It allows you to sandbox vagrant. so you can commit or rollback changes! https://github.com/jedi4ever/sahara
Why not https://github.com/dergachev/vagrant-vbox-snapshot ?It provides full snapshot abilities, so you can have multiple states.
Re: Vagrant: Create and configure portable development environments
#33We switched from hand-configured boxes and a long, "full stack local" setup document to chef + vagrant at my current company ( http://parse.ly ). Though it caused some kicking & screaming on the development team, the end result is that every developer has the same development environment, which pretty much matches our deployment environment (in Rackspace Cloud). I also just kicked off our summer intern class, and the…
What is chef mate?
Re: Vagrant: Create and configure portable development environments
#34I have never heard of Vagrant. The home page is, as usual, devoid of information. This is what Wikipedia says:
> Vagrant (software)
> From Wikipedia, the free encyclopedia
> Vagrant is open-source software for creating and configuring virtual development environments. It can be considered a wrapper around VirtualBox and configuration management software such as Chef, Salt and Puppet. Although written in Ruby, it is usable in other programming projects such as PHP, Python, Java, and C#.
Re: Vagrant: Create and configure portable development environments
#35Has anyone had much luck using Chef solo to provision their Vagrant box AND their production/staging environments? I'm currently attempting this, and it has been kind of a pain in the ass. Chef-solo seems woefully underpowered.
Had the same issue. Puppet is a little better suited, but also a pain.
Re: Vagrant: Create and configure portable development environments
#36Vagrant looks interesting but I am not sure why I would use it. Almost all of my work involves using Clojure and I default to using Postgres except in exceptional circumstances. It is so easy to have the same setup on my OS X and Linux laptops as my servers. I have never run into any compatibility problems, at least that I am aware of. Vagrant looks more useful for systems with lots of moving parts. I am starting a n…
I like to be able to script my environment and put it in a git repo for others who may join the team, or myself (when I repave my machine, for example). Also I've found the upfront effort to write the recipe (I tend to write lean recipes, rather than use community ones, as I see a lot of bloat and unneeded dependencies) helps me identify dependencies early on. (For example, say I need Selenium or Jenkins - my local machine's Java has been long working, so the cleanroom environment helps me identify gotchas I wouldn't otherwise see until deployment)
Re: Vagrant: Create and configure portable development environments
#37Vagrant creator here. What a pleasant surprise to see this pop up on HN this morning (it was unexpected, to be sure). I just want to shamelessly say that if you're more of a book person, the Vagrant O'Reilly book I wrote was just released this week, and it is a great way to get started: http://shop.oreilly.com/product/0636920026358.do Thanks! (And, hopefully as you know, as an author I make barely any royalties on an…
I'm curious, why the focus on development environments? How does it tie into production and staging environments?
Re: Vagrant: Create and configure portable development environments
#38Earlier quoted context omitted.
That's interesting. Have you ever considered Leanpub before you went with Oreilly?
I was approached by O'Reilly very early. I wasn't even considering writing a book prior to that. However, my experience with O'Reilly has been _fantastic_. I was never writing the book for money, I was writing it for publicity and to help push the project forward. For these reasons, O'Reilly was the clear winner. Additionally, everyone I've ever worked with at O'Reilly has been very professional, and they've been doi…
Okay, most important question time: Do you get to pick the animal? If so, why that particular pigeon?
Re: Vagrant: Create and configure portable development environments
#39I've used one VM for deploying my several small projects in the past. I'm definitely curious about separate sandboxes for them when developing locally - one chef-solo and vagrant instance for each - but it seems like it would be a lot more expensive to deploy them to separate boxes afterward. Is there an easy way to "merge" them back into one box when deploying?
... I guess that doesn't make sense. I should have the local vagrant/chef-solo mirror how I have my production server; all projects combined. But at least the chef recipes will make it easier to split things apart once I want to separate projects to different servers for traffic reasons.
Re: Vagrant: Create and configure portable development environments
#40We use Vagrant at Virgin Media in London. Great tool.
Ps. please fix the issue where on disconnect, you can't vagrant ssh back, the only fix I've found is to restart the vm using virtualbox.