
Stop Rebuilding Frontends for Every Environment
As a DevOps engineer, one frontend problem has always felt unnecessarily expensive to me: You build once for staging, then rebuild again for production because the frontend baked environment variables into the bundle. Same app. Same code. Different environment. Another build. That works, but it breaks one of the cleanest deployment ideas we have: build once, promote the same artifact everywhere. So I built clientshell . It lets you inject public runtime config into already-built frontend apps at container startup, without rebuilding for every environment. Docs: https://yonigofman.github.io/clientshell/ The problem Most frontend tooling treats environment variables as build-time values. That means if your app needs a different API URL, feature flag, analytics key, or public tenant setting in another environment, the artifact changes. So your pipeline ends up doing this: build for dev build for staging build for prod From a DevOps point of view, that is friction. It makes deployments slo
Continue reading on Dev.to
Opens in a new tab




