Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor errors in website vagrantup.com #37

Closed
jch opened this issue Mar 22, 2010 · 4 comments
Closed

Minor errors in website vagrantup.com #37

jch opened this issue Mar 22, 2010 · 4 comments

Comments

@jch
Copy link

jch commented Mar 22, 2010

I was following the 'Getting Started' guide and other online information and came across a handful of minor mistakes. I'm not sure where the static site files are kept, so I could not correct them by forking the project. Feel free to move this issue elsewhere if it's not appropriate for this repo.

Why

Each project depends on its own libraries, message queue systems, databases, framework, and more each with their own versions.

Boxes

Beginning running the following command so it can begin downloading while box installation is covered in more detail:

Link to vbox download seemed to be down, but http://download.virtualbox.org/virtualbox/3.1.4/ worked for me

Boxes

(the name of in the example is 'getting-started')
Note that the box is given its own name, in this case “rails.”

Packaging

(I see the mac address of the VM is what the example lists, but there is no 'more info' after this sentence)
And finally, we need to add in the MAC address of the virtual machine so the internet access will work on any machine (more on this later).

@mitchellh
Copy link
Contributor

Fix the basic typos/issues with getting started guide [closed by 8d5900a]

@mitchellh
Copy link
Contributor

Thanks for this =]

@jch
Copy link
Author

jch commented Mar 23, 2010

ah, it was in the 'docs' branch. Good job with the quick fix :)

@mitchellh
Copy link
Contributor

jch,

Right, to be specific, the "docs" branch represents the future-website. As I put in new features, bug fixes etc, I try to update the docs ASAP to match the changes so I don't forget about them later.

Then I merge the docs branch into gh-pages (the live site) when a version is released.

In the case of these quick fixes, I implemented the fixes directly on the live site, then cherry-picked the commits back into docs so they're reflected in the future as well.

Just posted this in case anyone is interested how the process (as it currently stands) works. Anyone is free to fork and provide pull requests for the docs branch :) as well as master and any other branch.

Mitchell

rogeriopradoj pushed a commit to FriendsOfVagrant/-legacy-friendsofvagrant.github.com that referenced this issue Nov 27, 2012
rogeriopradoj pushed a commit to FriendsOfVagrant/-legacy-friendsofvagrant.github.com that referenced this issue Nov 27, 2012
@ghost ghost locked and limited conversation to collaborators Apr 17, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants