Skip to content

Instantly share code, notes, and snippets.

@mraaroncruz
Created March 22, 2014 14:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mraaroncruz/9707759 to your computer and use it in GitHub Desktop.
Save mraaroncruz/9707759 to your computer and use it in GitHub Desktop.
vagrant talk discussion

Discussion below in comments

@mraaroncruz
Copy link
Author

Your talk looks like it could be perfect. I think it gets boring when all talks at a X meetup are about exactly X. And tools are awesome. Especially awesome tools like vagrant. I don't know who would say "Hey, this isn't about Javascript, WTF?!"

I was actually planning on using mongo or http://rethinkdb.com/ in my demo

@Sgoettschkes
Copy link

Yeah, I think 15 mins. are to short for both theory and a demo. What I could do is: Cut the theory by a few minutes, then do a demo with vagrant init, vagrant up and vagrant ssh.
From their you could take over, showing a more complex setup with provisioning going on, distributed systems or whatever you like. I'd love to see distribution especially as I only work with one box at a time and never tried setting up a more complex system.

@mraaroncruz
Copy link
Author

that sounds great.
FYI, I was going to use http://www.ansible.com/home to provision the boxes.
Maybe I will spend a couple minutes of my demo with an intro to that.
Or maybe we need a third person to do an ansible talk :P

@Sgoettschkes
Copy link

Ansible is great, but I don't use it for vagrant. I like it for setup of cloud machines because I don't need anything than my local ansible to get startet (Actually, I had a vagrant box with ansible installed and the playbooks to set up my boxes at hetzner and Digital Ocean). With chef, I'd need a server or get the cookbooks in there or whatever.

For vagrant, I use chef as it combines easy setup for most things and the possibility to do even the most complex things without workarounds.

@mraaroncruz
Copy link
Author

I moved from chef to ansible because ansible just feels right to me. Lots of ceremony with chef (and chef server - yikes!) way more features than I need for one to a few servers.
I also don't like to have vagrant provision for me because their provisioning API was another level of confusion between me and chef.
I will send you a link when i have my repo up so you can see what I mean. The only thing I miss in ansible is a way to specify a non-standard ssh-config file. Being able to keep my ssh config in my ansible repo would be awesome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment