Skip to content

feat(grafana): optional .grafana.env via GRAFANA_ENV_FILE, overridable GF_GITHUB_PLUGINS#6

Open
i-love-to-code wants to merge 2 commits intobartosian:mainfrom
veera-dao:feat/extend-grafana-config
Open

feat(grafana): optional .grafana.env via GRAFANA_ENV_FILE, overridable GF_GITHUB_PLUGINS#6
i-love-to-code wants to merge 2 commits intobartosian:mainfrom
veera-dao:feat/extend-grafana-config

Conversation

@i-love-to-code
Copy link
Copy Markdown
Contributor

This PR adds support for an optional Grafana configuration via an additional env file and makes the Grafana plugin list overridable from .env, without changing default behaviour for existing setups.

Changes

  • Optional Grafana env file: Grafana service uses env_file: ${GRAFANA_ENV_FILE:-/dev/null}.
    • Unset or omit GRAFANA_ENV_FILE and behaviour is unchanged (no extra file).
    • Set GRAFANA_ENV_FILE=.grafana.env in .env and create .grafana.env from .grafana.env.tmp to pass extra GF_* options to Grafana.
    • .grafana.env is in .gitignore.
  • Overridable GF_GITHUB_PLUGINS: In both docker-compose.yml and docker-compose.macos.yml, GF_GITHUB_PLUGINS is set via ${GF_GITHUB_PLUGINS:-"…"} so it can be overridden in .env while keeping the same default plugin URL.
  • Docs: README documents the optional Grafana customisation (copy .grafana.env.tmp.grafana.env, set GRAFANA_ENV_FILE=.grafana.env in .env). Sample .env in README and .env.tmp include commented GRAFANA_ENV_FILE and (where relevant) GF_GITHUB_PLUGINS. Fixed typos and Grafana docs link text.

Backwards compatibility

  • No new required env vars or files.
  • Default GRAFANA_ENV_FILE is /dev/null, so no file is required.
  • GF_GITHUB_PLUGINS default is unchanged; only overrides are new.
  • All existing environment vars remain and take precedence over the optional env file.

@i-love-to-code i-love-to-code marked this pull request as draft February 14, 2026 13:58
@i-love-to-code i-love-to-code marked this pull request as ready for review February 14, 2026 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant