inspec/www
Adam Moss 6cc94b554a fix(homebrew): correct homebrew installation command (#2832)
Signed-off-by: Adam Moss <adam.moss@bcs.org.uk>
2018-03-19 12:53:05 -04:00
..
data Fix links on docs page (#2716) 2018-02-20 14:41:58 -05:00
demo fix mobile (#2706) 2018-02-19 18:52:43 -08:00
lib Update InSpec website (#2681) 2018-02-17 07:44:42 -08:00
source fix(homebrew): correct homebrew installation command (#2832) 2018-03-19 12:53:05 -04:00
.gitignore rake to render all docs to www/ correctly with links 2016-09-26 06:21:05 +02:00
config.rb InSpec SEO (#2725) 2018-02-21 16:42:55 -08:00
config.ru Fixup rubocop violation in www/ 2016-09-13 15:11:48 +01:00
Gemfile InSpec SEO (#2725) 2018-02-21 16:42:55 -08:00
Rakefile move /tutorial to /demo (#2700) 2018-02-19 16:57:19 -08:00
README.md move /tutorial to /demo (#2700) 2018-02-19 16:57:19 -08:00

InSpec homepage

Development

Get all dependencies:

bundle install

To build the docs/ child pages run:

bundle exec rake docs

To run it live run:

bundle exec middleman server

For the online demo, take a look at www/demo.

Building

To build the site to a local static folder (without demo):

bundle exec middleman build

To build everything including the online demo:

bundle exec rake www:build

Releasing

To build everything and push a new version of the website, be in the www folder of this repository and run:

bundle install
bundle exec rake www

It will clear everything and build from scratch and create a local gh-pages branch with a static version of the website. Before pushing, it will ask you if you are happy with it.

Please verify the site now! To host the current folder you can run:

ruby -run -e httpd . -p 8000

Open your browser to localhost:8000.

If you are happy, you can confirm the site and let the release task push it live.

Flushing the Fastly Cache

The www Rake task will flush the cache at Fastly if you have the following environment variables set:

  • FASTLY_API_KEY
  • FASTLY_SERVICE_ID

These can be found in Chef's shared password manager. If these aren't set, the cache will not be flushed and will expire on its own. The cache can be flushed without doing a full website release by running rake www:flush