|
|
@ -63,10 +63,10 @@ installed in order to build the frontend assets.
|
|
|
|
You can directly use the `go` tool to download and install the `prometheus`
|
|
|
|
You can directly use the `go` tool to download and install the `prometheus`
|
|
|
|
and `promtool` binaries into your `GOPATH`:
|
|
|
|
and `promtool` binaries into your `GOPATH`:
|
|
|
|
|
|
|
|
|
|
|
|
$ GO111MODULE=on go get github.com/prometheus/prometheus/cmd/...
|
|
|
|
$ GO111MODULE=on go install github.com/prometheus/prometheus/cmd/...
|
|
|
|
$ prometheus --config.file=your_config.yml
|
|
|
|
$ prometheus --config.file=your_config.yml
|
|
|
|
|
|
|
|
|
|
|
|
*However*, when using `go get` to build Prometheus, Prometheus will expect to be able to
|
|
|
|
*However*, when using `go install` to build Prometheus, Prometheus will expect to be able to
|
|
|
|
read its web assets from local filesystem directories under `web/ui/static` and
|
|
|
|
read its web assets from local filesystem directories under `web/ui/static` and
|
|
|
|
`web/ui/templates`. In order for these assets to be found, you will have to run Prometheus
|
|
|
|
`web/ui/templates`. In order for these assets to be found, you will have to run Prometheus
|
|
|
|
from the root of the cloned repository. Note also that these directories do not include the
|
|
|
|
from the root of the cloned repository. Note also that these directories do not include the
|
|
|
|