One has to use "grafana/grafana" image - only using "grafana" will result in an error message like this: Error response from daemon: pull access denied for grafana, repository does not exist or may require 'docker login' It's a good idea to daemonize new container. The install instructions for Docker do this, and this instructions assume that running container already is daemonized (otherwise you wouldn't have to stop it). Best practise would be to create a new container, then stop old one and start new one - this would reduce downtime. To keep instructions simple and understandable, I didn't include that. |
||
---|---|---|
.. | ||
sources | ||
.gitignore | ||
logo-horizontal.png | ||
Makefile | ||
README.md | ||
versions.json |
Building the docs locally
When you contribute to documentation, it is a good practice to build the docs on your local machine to make sure your changes appear as you expect. This README explains the process for doing that.
Requirements
Docker >= 2.1.0.3
Build the doc site
- In the command line, make sure you are in the docs folder:
cd docs
. - Run
make docs
. This launches a preview of the docs website athttp://localhost:3002/docs/grafana/latest/
which will refresh automatically when changes to content in thesources
directory are made.
Content guidelines
Edit content in the sources
directory.
Using relref
for internal links
Use the Hugo shortcode relref any time you are linking to other internal docs pages.
Edit the side menu
Edit sources/menu.yaml to make changes to the sidebar. Stop and rerun the make docs
command for changes to take effect.
Add images
Images are currently hosted in the grafana/website repo.
Deploy changes to grafana.com
When a PR is merged to master with changes in the docs
directory, those changes are automatically synched to the grafana/website repo on the docs-grafana
branch.
In order to make those changes live, open a PR in the website repo that merges the docs-grafana
branch into master
. Then follow the publishing guidelines in that repo.