Repository navigation
feat(docker): add frontend live reload - #857
Merged
Merged
Conversation
jondricek
force-pushed
the
feat/live-reload-dev-workflow
branch
from
October 12, 2026 12:44
47aa499 to
d67ed7e
Compare
jondricek
force-pushed
the
feat/live-reload-dev-workflow
branch
from
October 12, 2026 13:00
d67ed7e to
b5a0c00
Compare
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## next #857 +/- ##
==========================================
- Coverage 49.47% 49.30% -0.18%
==========================================
Files 214 216 +2
Lines 29203 29362 +159
Branches 2365 2379 +14
==========================================
+ Hits 14448 14476 +28
- Misses 14666 14797 +131
Partials 89 89 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
🎉 This PR is included in version 4.17.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Summary
Configure the same frontend image for different Workbench instances without rebuilding Angular. Native commands and containers share a validated public configuration contract; the browser loads settings before bootstrap.
Adds a
devDocker target with Angular polling and same-origin API proxying. Production startup generates settings before Nginx starts; configuration responses useCache-Control: no-store. Build metadata stays separate. Documents native, container, and static-host configuration, and makes live REST API integration tests opt-in.Evidence
After: Runtime bootstrap tests cover mode defaults, shared immutable settings, meaningful empty/false overrides, and rejection of missing or invalid configuration before consumers start.
WORKBENCH_FRONTEND_TEST_API_URL; this CI result does not establish Compose compatibility or a published-image build.Merge Danger
Door: two-way
Revert the code and accompanying configuration changes. Merge before deployment PR #6.
Blast Radius: frontend
Affects startup, browser API routing, application settings, and production image entrypoint behavior. Invalid public settings prevent startup. Container environment changes require recreation; mounted JSON changes require restart and browser reload. Keep credentials in the REST API.
Related PRs