The benefits of the following "breaking change" are the following: - default behaviour naturally fits with most common usage (i.e. always connect with Vagrant SSH settings) - the autogenerated inventory is more consistent by providing both the SSH username and private key. - no longer needed to explain how to override Ansible `remote_user` parameters Important: With the `force_remote_user` option, people still can fall back to the former behavior (prior to Vagrant 1.8.0), which means that Vagrant integration capabilities are still quite open and flexible. |
||
---|---|---|
.. | ||
helpers | ||
lib | ||
source | ||
.buildpacks | ||
Gemfile | ||
Gemfile.lock | ||
Procfile | ||
README.md | ||
Vagrantfile | ||
config.rb | ||
config.ru |
README.md
Vagrant Documentation
This is the repository for the Vagrant Documentation website.
This is a Middleman project, which builds a static site from these source files. The site is hosted on Heroku and then fronted by Fastly.
Contributions Welcome!
If you find a typo or you feel like you can improve the HTML, CSS, or JavaScript, we welcome contributions. Feel free to open issues or pull requests like any normal GitHub project, and we'll merge it in.
Running the Site Locally
Running the site locally is simple. Clone this repo and run the following commands:
$ bundle
$ bundle exec middleman server
Then open up localhost:4567
. Note that some URLs you may need to append
".html" to make them work (in the navigation and such).