Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Adding more information about vagrant #223

Merged
merged 2 commits into from Dec 10, 2012

Conversation

Projects
None yet
2 participants
Contributor

Sgoettschkes commented Dec 9, 2012

I extracted the vagrant information into it's own section, adding more information.

@philsturgeon philsturgeon commented on an outdated diff Dec 9, 2012

_posts/01-06-01-Vagrant.md
@@ -0,0 +1,22 @@
+---
+isChild: true
+---
+
+## Vagrant {#vagrant_title}
+
+Running your application on different environments in development and production can lead to strange bugs
+popping up when you go live. It's also tricky to keep different development environments up to date with the same
+version for all libraries used when working with a team of developers.
+
+If you are developing on Windows and deploying to Linux (or anything non-Windows) or are developing in a team, you
+should consider using a virtual machine. This sounds tricky, but using [Vagrant][vagrant] you can set up a simple
+virtual machine with only a few steps. This so called "base boxes" can then be set up with different software
@philsturgeon

philsturgeon Dec 9, 2012

Collaborator

Should be "these based boxes"?

@philsturgeon philsturgeon commented on an outdated diff Dec 9, 2012

_posts/01-06-01-Vagrant.md
@@ -0,0 +1,22 @@
+---
+isChild: true
+---
+
+## Vagrant {#vagrant_title}
+
+Running your application on different environments in development and production can lead to strange bugs
+popping up when you go live. It's also tricky to keep different development environments up to date with the same
+version for all libraries used when working with a team of developers.
+
+If you are developing on Windows and deploying to Linux (or anything non-Windows) or are developing in a team, you
+should consider using a virtual machine. This sounds tricky, but using [Vagrant][vagrant] you can set up a simple
+virtual machine with only a few steps. This so called "base boxes" can then be set up with different software
+using either [Puppet][puppet] or [Chef][chef] (This is called provisioning). If you share those setup files with your
@philsturgeon

philsturgeon Dec 9, 2012

Collaborator

This would be better as:

can be set set up manually, or you can use "provisioning" software such as "Puppet" or "Chef" to do this for you. Provisioning the base box is a great way to ensure that multiple boxes are set up in an identical fashion, and removes the need for you to maintain complicated "set up" command lists, or bablabla

Something like that. Puppet and Chef need to be explained a little, they also need to sound optional - but explain why they SHOULD be used.

Thanks for this, its a good section!

Contributor

Sgoettschkes commented Dec 10, 2012

I inegrated your suggestions.

Regarding the explanation of Chef and Puppet: I can do this, but I don't know when I'll come around to do it.

I would suggest to merge this without the explanation on these two (if you're happy with the quality of the section of course) and I (or anybody else) do another PR later with more on provisioning.

philsturgeon pushed a commit that referenced this pull request Dec 10, 2012

Merge pull request #223 from Sgoettschkes/vagrant
Adding more information about vagrant

@philsturgeon philsturgeon merged commit e2885ad into codeguy:gh-pages Dec 10, 2012

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