fix(docker): set NODE_ENV=development - #271
Merged
Merged
Conversation
Agent-Logs-Url: https://github.com/radius-project/dashboard/sessions/351c71a9-496b-4a12-a931-c7ad6f111c8e Co-authored-by: DariuszPorowski <3431813+DariuszPorowski@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Set NODE_ENV to development in Dockerfile
fix: set NODE_ENV=development in Dockerfile
May 21, 2026
Member
|
@copilot just keep Dockerfile change, do not change CI |
Agent-Logs-Url: https://github.com/radius-project/dashboard/sessions/f46e78c8-ed60-404a-bcf9-aeac50b06cf9 Co-authored-by: DariuszPorowski <3431813+DariuszPorowski@users.noreply.github.com>
Contributor
Author
DariuszPorowski
marked this pull request as ready for review
May 21, 2026 15:51
DariuszPorowski
changed the title
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
brooke-hamilton
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
@backstage/plugin-auth-backend≥ 0.26.x silently disables the guest auth provider whenNODE_ENV=production. The dashboard Dockerfile has always setNODE_ENV=production, causing 401 "Missing credentials" on all pages after the Backstage dependency upgrade in #206. The Radius helm chart applied a workaround (radius-project/radius#11520); this moves the fix into the dashboard repo where it belongs.Changes
packages/backend/Dockerfile— ChangeENV NODE_ENV=production→ENV NODE_ENV=development; update comment to explain the Backstage auth requirement.Type of change
Screenshots
N/A — no UI changes.