-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3964 docker feature flags #3966
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next-js-prototype #3966 +/- ##
=====================================================
+ Coverage 77.56% 77.90% +0.33%
=====================================================
Files 467 467
Lines 14751 14712 -39
=====================================================
+ Hits 11442 11461 +19
+ Misses 3309 3251 -58 ☔ View full report in Codecov by Sentry. |
0562c8d
to
87d9758
Compare
87d9758
to
917d53b
Compare
The build script will either build the original UI or the NextJS UI, correct? And if the NextJS UI is built, then one is required to run the docker container by passing in FEATURE_FLAGS environment variable? Can we do it in a way that wouldn't require the user to pass the env variable, since the feature is set at build time? |
I talked with @VakarisZ about this and we want to toggle between these two UI's. If we pass the FEATURE_FLAGS to build the NextJS then we probably want to toggle between the two UI's, if not then we don't care. |
Also, do any additional ports need to be exposed in the docker container? I noticed we expose 5000 in the dockerfile, but the new UI uses 443 |
Wouldn't we need to build both then? Aren't we only building one currently? |
I'm not sure I follow. As written, this will build one UI or the other. You can switch them at build time, but you wouldn't be able to toggle between them at runtime. |
What does this PR do?
Fixes #3964
Running of docker with feature flags:
Or for multiple environments check this
PR Checklist
Testing Checklist