https://coreos.slack.com/archives/C023VGW21NU/p1650968332328829

We don't currently use FEC config helpers, maybe we should.
https://gitlab.cee.redhat.com/service/uhc-portal/-/blob/master/webpack.config.js

As a reminder, OCM only uses qa-beta, qa-stable (qaprodauth is our staging), prod-beta & prod-stable envs.

in development browser loads from https://prod.foo.redhat.com:1337/openshift
which we kept 2 ways to support:

1. yarn start-with-proxy [old mode, not sure any dev uses it still] — serve index.html containing ESI tags via insights-proxy resolving them on the fly. Backend API all routed via insights-proxy too.
2. yarn start: passes --env noproxy [this is what we normally run] — fetch snippets from https://console.redhat.com/[beta/]apps//chrome/snippets/head.html and body.html, inline them (using ReplaceWebpackPlugin) into index.html built by webpack. Backend APIs all routed via webpack's proxy.

The first mode is also what yarn build currently uses to produce index.html with ESI tags. example output: https://github.com/RedHatInsights/uhc-portal-frontend-deploy/blob/prod-stable/index.html

Do you recommend dropping insights-proxy entirely?