
* Add Grafana tutorials originally from tutorials repository Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Replace tutorials/step shortcode with ordinary headings Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix typos reported by codespell Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix doc-validator linting and run prettier Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Specify version in tutorials lookup as non-rendered pages do not have a relative permalink used to infer the version Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Use latest version Ensures CI passes and only breaks one website build as the backport to v9.3.x will solve the missing "latest" pages on publishing. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> --------- Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
1.2 KiB
title |
---|
Set up Environment |
Before you can get started building plugins, you need to set up your environment for plugin development.
To discover plugins, Grafana scans a plugin directory, the location of which depends on your operating system.
-
Create a directory called
grafana-plugins
in your preferred workspace. -
Find the
plugins
property in the Grafana configuration file and set theplugins
property to the path of yourgrafana-plugins
directory. Refer to the Grafana configuration documentation for more information.[paths] plugins = "/path/to/grafana-plugins"
-
Restart Grafana if it's already running, to load the new configuration.
Alternative method: Docker
If you don't want to install Grafana on your local machine, you can use Docker.
To set up Grafana for plugin development using Docker, run the following command:
docker run -d -p 3000:3000 -v "$(pwd)"/grafana-plugins:/var/lib/grafana/plugins --name=grafana grafana/grafana:7.0.0
Since Grafana only loads plugins on start-up, you need to restart the container whenever you add or remove a plugin.
docker restart grafana