vagrant/website
Brian Cain bcf4d5a210
Fixes #11228: Allow to force check for box updates
Prior to this commit, if a user had recently checked for updates, there
was no way to force Vagrant to re-check without manually deleting a
state file in the local `.vagrant` data dir. This commit fixes that by
giving users the ability to force check for updates for a given box with
a flag to the `vagrant box outdated` command.
2019-12-03 11:42:55 -08:00
..
scripts Update deploy process 2017-08-02 14:13:58 -04:00
source Fixes #11228: Allow to force check for box updates 2019-12-03 11:42:55 -08:00
Gemfile Update middleman-hashicorp container and Gemfile.lock 2019-08-21 16:08:55 -07:00
Gemfile.lock Update middleman-hashicorp container and Gemfile.lock 2019-08-21 16:08:55 -07:00
LICENSE.md Update license 2017-03-08 11:39:24 -08:00
Makefile Update middleman-hashicorp container and Gemfile.lock 2019-08-21 16:08:55 -07:00
README.md website/README: Add a link to CONTRIBUTING.md 2018-05-16 14:26:14 +02:00
config.rb Update website download version 2.2.6 2019-10-14 12:35:50 -07:00
redirects.txt Update deploy process 2017-08-02 14:13:58 -04:00

README.md

Vagrant Website

This subdirectory contains the entire source for the Vagrant Website. This is a Middleman project, which builds a static site from these source files.

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.

See also the Vagrant Contributing Guide for more details.

Running the Site Locally

Running the site locally is simple. Clone this repo and run make website.

Then open up http://localhost:4567. Note that some URLs you may need to append ".html" to make them work (in the navigation).