feat(issue-339): Adds config ability switch between branded content vs default #355
Conversation
This file contains 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
feat: configurable NODE_ENV feat: adding config files to retrieve env vars chore: minor clean up refactor: allowing parallel processes to run chore: clean up chore: clean up
chore: clean up
…anded/default logo
pattishin
added
the
tech: lit
engelke
approved these changes
Apr 21, 2022
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.
Depends on #356 to be merged first.
Resolves issue: #339
To verify locally:
experimental/client-app/server/proxy.js)See that the header changes according to
THEMEenvironment variable hardcoded inpackage.json. Currently just 2 options:cymbalbranding and default emblem branding.