Skip to content

Bug: Environment flag not respected when starting the Grafana server #2171

@mckn

Description

@mckn

Which package(s) does this bug affect?

  • Create Plugin
  • Sign Plugin
  • Plugin E2E
  • Plugin Meta Extractor
  • Plugin ESLint Rules

Package versions

What happened?

When you change the development flag, to get Grafana to run in production, while running docker-compose it won't be respected. Looks like one of the reasons is line 19 in the .config/Dockerfile. It is setting the ENV GF_DEFAULT_APP_MODE "development" always regardless of what the passed development flag is set to.

What you expected to happen

I want to test running Grafana in production mode.

How to reproduce it (as minimally and precisely as possible)

  1. Scaffold a new plugin
  2. Try to build the plugin and run Grafana in production mode.
  3. Open the browser and inspect the build settings
  4. The buildInfo.env flag is still set to development

Environment

n/a

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    patchIncrement the patch version when mergedtype/bugSomething isn't working

    Type

    Projects

    Status

    📅 Planned

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions