Chore: Hugo upgrade (#17494)

* Fix: Upgrade hugo wip * Chore: Rename index to _index for latest hugo * Chore: Use relative refs, no starting slash * Feat: Add possibility to mount layouts from grafana.org project

Chore: Hugo upgrade (#17494)
* Fix: Upgrade hugo wip * Chore: Rename index to _index for latest hugo * Chore: Use relative refs, no starting slash * Feat: Add possibility to mount layouts from grafana.org project
3da8cff6 · Johannes Schill · GitHub · ab4e1526 · 3da8cff6 · 3da8cff6
Commit 3da8cff6 authored Jun 12, 2019 by Johannes Schill Committed by GitHub Jun 12, 2019
40 changed files
--- a/docs/Makefile
+++ b/docs/Makefile
@@ -4,12 +4,16 @@
 DOCSPORT := 3004

 DOCKER_DOCS_IMAGE := grafana/grafana-docs
-
 SOURCES_HOST_DIR := "$(shell pwd)/sources"

+# assuming grafana and grafana.org-repo to be checked out in the same folder
+DEFAULT_LAYOUTS_DIR := "$(shell pwd)/../../../../../../grafana.org/layouts"
+
+# to allow `make DOCSDIR=docs docs-shell` (to create a bind mount in docs)
+LAYOUTS_MOUNT := $(if $(LAYOUTS),-v $(DEFAULT_LAYOUTS_DIR):/site/layouts)
 DOCS_MOUNT := -v $(SOURCES_HOST_DIR):/site/content

-DOCKER_RUN_DOCS := docker run --rm -it $(DOCS_MOUNT) -e NOCACHE -p 3004:3004 -p 3005:3005
+DOCKER_RUN_DOCS := docker run --rm -it $(DOCS_MOUNT) $(LAYOUTS_MOUNT) -e NOCACHE -p 3004:3004 -p 3005:3005

 VERSION := $(shell head -n 1 VERSION)

@@ -24,7 +28,7 @@ docs: docs-build
 	$(DOCKER_RUN_DOCS) $(DOCS_MOUNT) -e DOCKERHOST "$(DOCKER_DOCS_IMAGE)" /bin/bash -c "grunt --env=dev-docs && grunt connect --port=3004"

 watch: docs-build
-	$(DOCKER_RUN_DOCS) $(DOCS_MOUNT) -e DOCKERHOST "$(DOCKER_DOCS_IMAGE)" /bin/bash -c "grunt --env=dev-docs && grunt connect --port=3004 & grunt watch --port=3004 --env=dev-docs"
+	$(DOCKER_RUN_DOCS) $(DOCS_MOUNT) $(LAYOUTS_MOUNT) -e DOCKERHOST "$(DOCKER_DOCS_IMAGE)" /bin/bash -c "grunt --env=dev-docs && grunt connect --port=3004 & grunt watch --port=3004 --env=dev-docs"

 publish: checkvars docs-build
 	$(info Publishing ENV=${ENV} and VERSION=${VERSION})

--- a/docs/sources/index.md
+++ b/docs/sources/index.md
@@ -3,7 +3,7 @@ title = "Grafana documentation"
 description = "Guides, Installation & Feature Documentation"
 keywords = ["grafana", "installation", "documentation"]
 type = "docs"
-aliases = ["v1.1", "guides/reference/admin", "v3.1"]
+aliases = ["/v1.1", "/guides/reference/admin", "/v3.1"]
 +++

 # Grafana Documentation

--- a/docs/sources/administration/index.md
+++ b/docs/sources/administration/index.md
--- a/docs/sources/administration/cli.md
+++ b/docs/sources/administration/cli.md
@@ -16,7 +16,7 @@ Grafana cli is a small executable that is bundled with Grafana-server and is sup

 The CLI allows you to install, upgrade and manage your plugins on the machine it is running on.
 You can find more information about how to install and manage your plugins in the
-[plugins page]({{< relref "plugins/installation.md" >}}).
+[plugins page]({{< relref "../plugins/installation.md" >}}).

 ## Admin


--- a/docs/sources/alerting/index.md
+++ b/docs/sources/alerting/index.md
--- a/docs/sources/auth/index.md
+++ b/docs/sources/auth/index.md
--- a/docs/sources/auth/enhanced_ldap.md
+++ b/docs/sources/auth/enhanced_ldap.md
@@ -12,7 +12,7 @@ weight = 3

 # Enhanced LDAP Integration

-> Enhanced LDAP Integration is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise/index.md" >}}).
+> Enhanced LDAP Integration is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise" >}}).

 The enhanced LDAP integration adds additional functionality on top of the [existing LDAP integration]({{< relref "auth/ldap.md" >}}).


--- a/docs/sources/contribute/index.md
+++ b/docs/sources/contribute/index.md
--- a/docs/sources/enterprise/index.md
+++ b/docs/sources/enterprise/index.md
--- a/docs/sources/features/index.md
+++ b/docs/sources/features/index.md
--- a/docs/sources/features/datasources/index.md
+++ b/docs/sources/features/datasources/index.md
--- a/docs/sources/features/datasources/azuremonitor.md
+++ b/docs/sources/features/datasources/azuremonitor.md
@@ -144,7 +144,7 @@ Examples:

 {{< docs-imagebox img="/img/docs/v60/azuremonitor-service-variables.png" class="docs-image--no-shadow" caption="Nested Azure Monitor Template Variables" >}}

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Azure Monitor Metrics Whitelist
@@ -196,7 +196,7 @@ Examples:

 Use the one of the following queries in the `Query` field in the Variable edit view.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 | Name                               | Description                                                |
@@ -268,7 +268,7 @@ To make writing queries easier there are several Grafana macros that can be used

 There are also some Grafana variables that can be used in Azure Log Analytics queries:

- `$__interval` - Grafana calculates the minimum time grain that can be used to group by time in queries. More details on how it works [here]({{< relref "reference/templating.md#interval-variables" >}}). It returns a time grain like `5m` or `1h` that can be used in the bin function. E.g. `summarize count() by bin(TimeGenerated, $__interval)`
+- `$__interval` - Grafana calculates the minimum time grain that can be used to group by time in queries. More details on how it works [here]({{< relref "../../reference/templating.md#interval-variables" >}}). It returns a time grain like `5m` or `1h` that can be used in the bin function. E.g. `summarize count() by bin(TimeGenerated, $__interval)`

 ### Azure Log Analytics Alerting


--- a/docs/sources/features/datasources/cloudwatch.md
+++ b/docs/sources/features/datasources/cloudwatch.md
@@ -130,7 +130,7 @@ Instead of hard-coding things like server, application and sensor name in you me
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Query variable

--- a/docs/sources/features/datasources/elasticsearch.md
+++ b/docs/sources/features/datasources/elasticsearch.md
@@ -108,7 +108,7 @@ Instead of hard-coding things like server, application and sensor name in you me
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Query variable

--- a/docs/sources/features/datasources/graphite.md
+++ b/docs/sources/features/datasources/graphite.md
@@ -91,7 +91,7 @@ Instead of hard-coding things like server, application and sensor name in you me
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 Graphite 1.1 introduced tags and Grafana added support for Graphite queries with tags in version 5.0. To create a variable using tag values, then you need to use the Grafana functions `tags` and `tag_values`.
@@ -140,7 +140,7 @@ Example of a tag expression with regex formatting and using the Equal Tilde oper
 server=~${servers:regex}
 ```

-Checkout the [Advanced Formatting Options section in the Variables]({{< relref "reference/templating.md#advanced-formatting-options" >}}) documentation for examples and details.
+Checkout the [Advanced Formatting Options section in the Variables]({{< relref "../../reference/templating.md#advanced-formatting-options" >}}) documentation for examples and details.

 ## Annotations


--- a/docs/sources/features/datasources/influxdb.md
+++ b/docs/sources/features/datasources/influxdb.md
@@ -124,7 +124,7 @@ Instead of hard-coding things like server, application and sensor name in you me
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Query variable

--- a/docs/sources/features/datasources/mssql.md
+++ b/docs/sources/features/datasources/mssql.md
@@ -300,7 +300,7 @@ Any series lacking a value in a 3 minute window will have a value of zero which 

 Instead of hard-coding things like server, application and sensor name in you metric queries you can use variables in their place. Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different types of template variables.
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different types of template variables.

 ### Query Variable

@@ -370,7 +370,7 @@ Grafana automatically creates a quoted, comma-separated string for multi-value v

 `${servers:csv}`

-Read more about variable formatting options in the [Variables]({{< relref "reference/templating.md#advanced-formatting-options" >}}) documentation.
+Read more about variable formatting options in the [Variables]({{< relref "../../reference/templating.md#advanced-formatting-options" >}}) documentation.

 ## Annotations


--- a/docs/sources/features/datasources/mysql.md
+++ b/docs/sources/features/datasources/mysql.md
@@ -238,7 +238,7 @@ This feature is currently available in the nightly builds and will be included i

 Instead of hard-coding things like server, application and sensor name in you metric queries you can use variables in their place. Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different types of template variables.
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different types of template variables.

 ### Query Variable

@@ -316,7 +316,7 @@ Grafana automatically creates a quoted, comma-separated string for multi-value v

 `${servers:csv}`

-Read more about variable formatting options in the [Variables]({{< relref "reference/templating.md#advanced-formatting-options" >}}) documentation.
+Read more about variable formatting options in the [Variables]({{< relref "../../reference/templating.md#advanced-formatting-options" >}}) documentation.

 ## Annotations


--- a/docs/sources/features/datasources/opentsdb.md
+++ b/docs/sources/features/datasources/opentsdb.md
@@ -53,7 +53,7 @@ Instead of hard-coding things like server, application and sensor name in you me
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Query variable

--- a/docs/sources/features/datasources/postgres.md
+++ b/docs/sources/features/datasources/postgres.md
@@ -242,7 +242,7 @@ ORDER BY time

 Instead of hard-coding things like server, application and sensor name in you metric queries you can use variables in their place. Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different types of template variables.
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different types of template variables.

 ### Query Variable

@@ -318,7 +318,7 @@ Grafana automatically creates a quoted, comma-separated string for multi-value v

 `${servers:csv}`

-Read more about variable formatting options in the [Variables]({{< relref "reference/templating.md#advanced-formatting-options" >}}) documentation.
+Read more about variable formatting options in the [Variables]({{< relref "../../reference/templating.md#advanced-formatting-options" >}}) documentation.

 ## Annotations


--- a/docs/sources/features/datasources/prometheus.md
+++ b/docs/sources/features/datasources/prometheus.md
@@ -61,7 +61,7 @@ Instead of hard-coding things like server, application and sensor name in your m
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Query variable

--- a/docs/sources/features/datasources/stackdriver.md
+++ b/docs/sources/features/datasources/stackdriver.md
@@ -172,7 +172,7 @@ Instead of hard-coding things like server, application and sensor name in you me
 Variables are shown as dropdown select boxes at the top of the dashboard. These dropdowns makes it easy to change the data
 being displayed in your dashboard.

-Checkout the [Templating]({{< relref "reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
+Checkout the [Templating]({{< relref "../../reference/templating.md" >}}) documentation for an introduction to the templating feature and the different
 types of template variables.

 ### Query Variable

--- a/docs/sources/features/panels/index.md
+++ b/docs/sources/features/panels/index.md
--- a/docs/sources/features/panels/graph.md
+++ b/docs/sources/features/panels/graph.md
@@ -33,7 +33,7 @@ The general tab allows customization of a panel's appearance and menu options.
 - **Transparent** - If checked, removes the solid background of the panel (default not checked).

 ### Repeat
-Repeat a panel for each value of a variable.  Repeating panels are described in more detail [here]({{< relref "reference/templating.md#repeating-panels" >}}).
+Repeat a panel for each value of a variable.  Repeating panels are described in more detail [here]({{< relref "../../reference/templating.md#repeating-panels" >}}).

 ### Drilldown / detail link


--- a/docs/sources/guides/index.md
+++ b/docs/sources/guides/index.md
--- a/docs/sources/http_api/index.md
+++ b/docs/sources/http_api/index.md
@@ -18,13 +18,13 @@ dashboards, creating users and updating data sources.
 ## Supported HTTP APIs:


-* [Authentication API]({{< relref "/http_api/auth.md" >}})
-* [Dashboard API]({{< relref "/http_api/dashboard.md" >}})
+* [Authentication API]({{< relref "http_api/auth.md" >}})
+* [Dashboard API]({{< relref "http_api/dashboard.md" >}})
 * [Dashboard Versions API]({{< relref "http_api/dashboard_versions.md" >}})
 * [Dashboard Permissions API]({{< relref "http_api/dashboard_permissions.md" >}})
-* [Folder API]({{< relref "/http_api/folder.md" >}})
+* [Folder API]({{< relref "http_api/folder.md" >}})
 * [Folder Permissions API]({{< relref "http_api/folder_permissions.md" >}})
-* [Folder/dashboard search API]({{< relref "/http_api/folder_dashboard_search.md" >}})
+* [Folder/dashboard search API]({{< relref "http_api/folder_dashboard_search.md" >}})
 * [Data Source API]({{< relref "http_api/data_source.md" >}})
 * [Organization API]({{< relref "http_api/org.md" >}})
 * [Snapshot API]({{< relref "http_api/snapshot.md" >}})

--- a/docs/sources/http_api/datasource_permissions.md
+++ b/docs/sources/http_api/datasource_permissions.md
@@ -11,7 +11,7 @@ parent = "http_api"

 # Datasource Permissions API

-> Datasource Permissions is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise/index.md" >}}).
+> Datasource Permissions is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise" >}}).

 This API can be used to enable, disable, list, add and remove permissions for a datasource.


--- a/docs/sources/http_api/external_group_sync.md
+++ b/docs/sources/http_api/external_group_sync.md
@@ -11,7 +11,7 @@ parent = "http_api"

 # External Group Synchronization API

-> External Group Synchronization is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise/index.md" >}}).
+> External Group Synchronization is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise" >}}).

 ## Get External Groups


--- a/docs/sources/installation/index.md
+++ b/docs/sources/installation/index.md
--- a/docs/sources/installation/configuration.md
+++ b/docs/sources/installation/configuration.md
@@ -389,14 +389,14 @@ Text used as placeholder text on login page for password input.
 Grafana provides many ways to authenticate users. The docs for authentication has been split in to many different pages
 below.

- [Authentication Overview]({{< relref "auth/overview.md" >}}) (anonymous access options, hide login and more)
- [Google OAuth]({{< relref "auth/google.md" >}}) (auth.google)
- [GitHub OAuth]({{< relref "auth/github.md" >}}) (auth.github)
- [Gitlab OAuth]({{< relref "auth/gitlab.md" >}}) (auth.gitlab)
- [Generic OAuth]({{< relref "auth/generic-oauth.md" >}}) (auth.generic_oauth, okta2, auth0, bitbucket, azure)
- [Basic Authentication]({{< relref "auth/overview.md" >}}) (auth.basic)
- [LDAP Authentication]({{< relref "auth/ldap.md" >}}) (auth.ldap)
- [Auth Proxy]({{< relref "auth/auth-proxy.md" >}}) (auth.proxy)
+- [Authentication Overview]({{< relref "../auth/overview.md" >}}) (anonymous access options, hide login and more)
+- [Google OAuth]({{< relref "../auth/google.md" >}}) (auth.google)
+- [GitHub OAuth]({{< relref "../auth/github.md" >}}) (auth.github)
+- [Gitlab OAuth]({{< relref "../auth/gitlab.md" >}}) (auth.gitlab)
+- [Generic OAuth]({{< relref "../auth/generic-oauth.md" >}}) (auth.generic_oauth, okta2, auth0, bitbucket, azure)
+- [Basic Authentication]({{< relref "../auth/overview.md" >}}) (auth.basic)
+- [LDAP Authentication]({{< relref "../auth/ldap.md" >}}) (auth.ldap)
+- [Auth Proxy]({{< relref "../auth/auth-proxy.md" >}}) (auth.proxy)

 ## [dataproxy]


--- a/docs/sources/installation/debian.md
+++ b/docs/sources/installation/debian.md
@@ -146,10 +146,10 @@ those options.

 ### Adding data sources

- [Graphite]({{< relref "features/datasources/graphite.md" >}})
- [InfluxDB]({{< relref "features/datasources/influxdb.md" >}})
- [OpenTSDB]({{< relref "features/datasources/opentsdb.md" >}})
- [Prometheus]({{< relref "features/datasources/prometheus.md" >}})
+- [Graphite]({{< relref "../features/datasources/graphite.md" >}})
+- [InfluxDB]({{< relref "../features/datasources/influxdb.md" >}})
+- [OpenTSDB]({{< relref "../features/datasources/opentsdb.md" >}})
+- [Prometheus]({{< relref "../features/datasources/prometheus.md" >}})

 ## Installing from binary tar file


--- a/docs/sources/permissions/index.md
+++ b/docs/sources/permissions/index.md
--- a/docs/sources/permissions/datasource_permissions.md
+++ b/docs/sources/permissions/datasource_permissions.md
@@ -12,7 +12,7 @@ weight = 4

 # Datasource Permissions

-> Datasource Permissions is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise/index.md" >}}).
+> Datasource Permissions is only available in Grafana Enterprise. Read more about [Grafana Enterprise]({{< relref "enterprise" >}}).

 Datasource permissions allows you to restrict access for users to query a datasource. For each datasource there is
 a permission page that makes it possible to enable permissions and restrict query permissions to specific

--- a/docs/sources/plugins/index.md
+++ b/docs/sources/plugins/index.md
--- a/docs/sources/project/index.md
+++ b/docs/sources/project/index.md
-++
+++
 title = "Project"
 type = "docs"
 identifier = "project"

--- a/docs/sources/reference/index.md
+++ b/docs/sources/reference/index.md
--- a/docs/sources/reference/dashboard_folders.md
+++ b/docs/sources/reference/dashboard_folders.md
@@ -47,6 +47,6 @@ The Dashboard Folder Page is similar to the Manage Dashboards page and is where 

 Permissions can assigned to a folder and inherited by the containing dashboards. An Access Control List (ACL) is used where
 **Organization Role**, **Team** and Individual **User** can be assigned permissions. Read the
- [Dashboard & Folder Permissions]({{< relref "permissions/dashboard_folder_permissions.md" >}}) docs for more detail
+ [Dashboard & Folder Permissions]({{< relref "../permissions/dashboard_folder_permissions.md" >}}) docs for more detail
 on the permission system.

--- a/docs/sources/tutorials/index.md
+++ b/docs/sources/tutorials/index.md
--- a/docs/sources/tutorials/ha_setup.md
+++ b/docs/sources/tutorials/ha_setup.md
@@ -21,7 +21,7 @@ Setting up Grafana for high availability is fairly simple. It comes down to two 
 ## Configure multiple servers to use the same database

 First, you need to do is to setup MySQL or Postgres on another server and configure Grafana to use that database.
-You can find the configuration for doing that in the [[database]]({{< relref "configuration.md" >}}#database) section in the grafana config.
+You can find the configuration for doing that in the [[database]]({{< relref "../installation/configuration.md" >}}#database) section in the grafana config.
 Grafana will now persist all long term data in the database. How to configure the database for high availability is out of scope for this guide. We recommend finding an expert on for the database you're using.

 ## Alerting
@@ -31,7 +31,7 @@ Currently alerting supports a limited form of high availability. Since v4.2.0, a
 ## User sessions

 > After Grafana 6.2 you don't need to configure session storage since the database will be used by default.
-> If you want to offload the login session data from the database you can configure [remote_cache]({{< relref "configuration.md" >}}#remote-cache)
+> If you want to offload the login session data from the database you can configure [remote_cache]({{< relref "../installation/configuration.md" >}}#remote-cache)

 The second thing to consider is how to deal with user sessions and how to configure your load balancer in front of Grafana.
 Grafana supports two ways of storing session data: locally on disk or in a database/cache-server.
@@ -44,7 +44,7 @@ stored on disk rather than on a shared database. This is the default behavior fo

 ### Stateless sessions
 You can also choose to store session data in a Redis/Memcache/Postgres/MySQL which means that the load balancer can send a user to any Grafana server without having to log in on each server. This requires a little bit more work from the operator but enables you to remove/add grafana servers without impacting the user experience.
-If you use MySQL/Postgres for session storage, you first need a table to store the session data in. More details about that in [[sessions]]({{< relref "configuration.md" >}}#session)
+If you use MySQL/Postgres for session storage, you first need a table to store the session data in. More details about that in [[sessions]]({{< relref "../installation/configuration.md" >}}#session)

 For Grafana itself it doesn't really matter if you store the session data on disk or database/redis/memcache. But we recommend using a database/redis/memcache since it makes it easier manage the grafana servers.


--- a/packages/grafana-runtime/package.json
+++ b/packages/grafana-runtime/package.json
@@ -16,8 +16,7 @@
  },
  "author": "Grafana Labs",
  "license": "Apache-2.0",
-  "dependencies": {
-  },
+  "dependencies": {},
  "devDependencies": {
    "awesome-typescript-loader": "^5.2.1",
    "lodash": "^4.17.10",