So far every prometheus/alertmanater/... release branch had to be
manually configured in the nanoc.yaml config file. With this change the
most recent release branches will be checked out automatically if a
corresponding semver tag exists.
As the Prometheus git repository includes several hundreds of megabytes
of vendored assets, the repository is cloned bare and all blobs are
filtered by default. Each version is then checked out in an individual
working tree and git's spare-chekcout feature is used to reduce the
checkout to the `docs/` folder. The git data is cached in
`tmp/repo_docs/` and will be recreated automatically if removed.
Signed-off-by: Tobias Schmidt <tobidt@gmail.com>
* Update Ruby gems.
* Remove nanoc-cachebuster due to incompatibility.
* Add README item about GitHub auth to improve build reliability.
* Fix various required config changes for 4.0
Signed-off-by: Ben Kochie <superq@gmail.com>
Let the governance use the default layout (all markdown files default to
"docs").
Make the default layout use the right div classes so the CSS can take
hold.
Fix the `layout` declaration for Markdown documents that are not `kind:
article`. Declare the governance to use the "default" layout, not the
"docs" one. This is the minimal change to support the governance
document. The layout choice needs a refactoring, but how to do that
needs more thought.
With this commit it becomes possible to define additional data sources
for content pages. The content will be cloned from the specified
repository. Links in these pages will be normalized to work inside the
docs project. It's assumed the documentation pages include the standard
nanoc config options and set :title and optionall :sort_rank.
This is based roughly on
http://clarkdave.net/2012/02/building-a-static-blog-with-nanoc/
with a lot of small modifications to make it fit the existing docs site.
Blog posts should be added as:
content/blog/YYYY-MM-DD-post-title.md
They need to state the title, kind, created_at, and author in the
frontmatter, e.g.:
---
title: "This is a blog post title"
created_at: 2015-04-22
kind: article
author: Julius Volz
---
Add links to client code for the pushgateway.
Make getting started link on frontpage go to Getting started section.
Put exposition formats at the end of instrumenting, as it's the least relevant
to normal users.
