|
@@ -24,7 +24,7 @@ For every push event on the `master` branch of the repository, it will look at t
|
24
|
24
|
|
25
|
25
|
It will then call the puller to have all the files up to date. This is mainly done to update the version number of each dashboard, as Grafana updates them automatically when a new or updated dashboard is pushed.
|
26
|
26
|
|
27
|
|
-Please note that the pusher currently only pushes new or modified dashboards to the Grafana API. If the file for a dashboard is removed from the Git repository, the dashboard won't be deleted on the Gragana instance.
|
|
27
|
+Please note that the pusher currently only pushes new or modified dashboards to the Grafana API. If the file for a dashboard is removed from the Git repository, the dashboard won't be deleted on the Grafana instance.
|
28
|
28
|
|
29
|
29
|
Because it hosts a webserver, the pusher runs as a daemon and never exists unless it `panic`s because of an error, or it is killed (e.g. with `Ctrl+C`).
|
30
|
30
|
|