Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One of the biggest strengths for Vagrant is Chef (or Puppet if you prefer). Anything that requires "apt-get *" as part of your instructions after "vagrant up" and you're just doing it wrong.

Check your Vagrantfile and associated recipes into git. Then it's just "git clone; vagrant up"

The benefit of this is that you can share your stack by having someone else just git clone your stack. Rather than a blog post, we'd be looking at your chef recipe. I'd much prefer that.



Thanks for the feedback. I use Puppet too, but avoided it in the post to simplify it for the reader. Maybe I'll write a follow-up and include Puppet as well.


Please write this follow-up.

I've known about Puppet for a while (Chef is new to me) and I've yet to see a tutorial here on HN on how to get up and running with either.


How big is the performance hit from the virtualization in your experience?




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: