The environment.ts file is the natural starting point for managing configuration in an Angular application, but it doesn’t always cut it.
When we’re talking about enterprise-grade applications deployed across dozens or even hundreds of clients, environment.ts is no longer the best approach for handling configuration.
In this article, I’ll explain how I managed configuration in a SaaS Angular application deployed across more than 300 clients.
<a href="https://www.thinkasadev.com/en/angular-config-from-environment-ts-to-http-entpoint/" target="_blank" rel="noopener nofollow">https://www.thinkasadev.com/en/angular-config-from-environment-ts-to-http-entpoint/</a>

Giorgio

Managing configuration in Angular via environment.ts works for simple cases, but falls short for enterprise SaaS applications deployed across hundreds of clients. This post walks through an approach used in a real-world Angular SaaS app with 300+ client deployments, moving configuration management from static environment files to a dynamic HTTP endpoint solution.

Angular config: from environment.ts to http entpoint