8f59f89a2e
This is the result of an unhappy customer who raised a very valid point. If you are not on the Vagrant mailing list, you would be unaware that upgrading VMware would cause your plugin to stop functioning. While this does not solve the problem of dispersing that information, it helps clarify that plugin version support is for the latest version of the Vagrant plugin and does not extend to previous ones. |
||
---|---|---|
.. | ||
helpers | ||
lib | ||
source | ||
.buildpacks | ||
Gemfile | ||
Gemfile.lock | ||
Procfile | ||
README.md | ||
Vagrantfile | ||
config.rb | ||
config.ru | ||
version.txt |
README.md
VagrantUp.com
This is the repository for the Vagrant 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).