Skip to content

Fix: empty publicRuntimeEnvironment in docker and Kubernetes#662

Closed
dkyeremeh wants to merge 1 commit intothedevs-network:developfrom
dkyeremeh:fix-publicRuntimeConfig
Closed

Fix: empty publicRuntimeEnvironment in docker and Kubernetes#662
dkyeremeh wants to merge 1 commit intothedevs-network:developfrom
dkyeremeh:fix-publicRuntimeConfig

Conversation

@dkyeremeh
Copy link
Copy Markdown

@dkyeremeh dkyeremeh commented Dec 7, 2022

Fixes #656 #636

Issue #656 occurs because the configuration DISALLOW_ANONYMOUS_LINKS is not available to publicRuntimeConfig
when using container orchestration.

This PR allows both .env file and values from process.env to be used to configure app, making it possible to use any type of environmental variables

@dkyeremeh
Copy link
Copy Markdown
Author

Looks like #637 addresses the same issue using a different approach

@dkyeremeh
Copy link
Copy Markdown
Author

@fashberg what do you think about this approach?

Comment thread client/consts/consts.ts
Comment on lines +5 to +6
export const { DISALLOW_ANONYMOUS_LINKS } = publicRuntimeConfig;
export const { DISALLOW_REGISTRATION } = publicRuntimeConfig;
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No longer necessary to compare the value with 'true'

@poeti8 poeti8 closed this Jan 8, 2025
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.

Not show the homepage with options if anonymous links disabled

2 participants