DEV Community

Discussion on: Does your UI use "build once" for promoting to environments?

Collapse
 
winstonpuckett profile image
Winston Puckett

We use a build once approach. We have a .Net app and anything that needs to change between Dev, QA, QA2, Demo, Test, and Prod is a configuration for the environment either in the App Service itself or in our External Config service.

I like this approach, and as we're moving things to containers, it seems to fit even better.

Collapse
 
manishfoodtechs profile image
manish srivastava

+1

Collapse
 
dgreene1 profile image
Dan Greene

That's an interesting idea. I hadn't thought of a config service. That is a bit strange to me in the React world since I'm used to having the UI be completely decoupled from the backend (i.e. there's no .NET anywhere). And in that world, the config typically is stored in the source control next to the React code.

But I do think your idea would work. Pretty cool. I've also considered LaunchDarkly as a way to store the config.

Collapse
 
winstonpuckett profile image
Winston Puckett

Here's the one we use - azure.microsoft.com/en-us/updates/...

Yeah, I would prefer a JAMStack approach, but MVC is pretty tightly coupled at this point. We use a C# library call, but I think there's also a rest API you could use with this service.