inspec/www
Stephan Renatus 222dd6107f [www] fix typo
Signed-off-by: Stephan Renatus <srenatus@chef.io>
2017-05-02 11:46:01 +02:00
..
data Add docs for habitat CLI commands 2017-03-28 13:59:38 -04:00
lib Address rubocop violations 2017-02-08 16:49:16 -06:00
source [www] fix typo 2017-05-02 11:46:01 +02:00
tutorial Address rubocop violations 2017-02-08 16:49:16 -06:00
.gitignore rake to render all docs to www/ correctly with links 2016-09-26 06:21:05 +02:00
config.rb Fix ServerSpec migration doc rendering 2017-05-01 15:18:49 -05:00
config.ru Fixup rubocop violation in www/ 2016-09-13 15:11:48 +01:00
Gemfile Add rake task for flushing Fastly cache 2017-04-28 14:22:00 -04:00
Gemfile.lock Add rake task for flushing Fastly cache 2017-04-28 14:22:00 -04:00
Rakefile Add rake task for flushing Fastly cache 2017-04-28 14:22:00 -04:00
README.md Add rake task for flushing Fastly cache 2017-04-28 14:22:00 -04:00

InSpec homepage

Development

Get all dependencies:

bundle install

To run it live run:

bundle exec middleman server

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

Building

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

bundle exec middleman build

To build everything including the online tutorial:

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