You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are relevant/related to the feature request?
No response
Description
There is a nice ability in angular to define multiple environments and have a different build per each of them.
The only problem is that environment file is NOT configurable on prod but there are settings need that ability for us,
for example: "serverApiUrl" which we need to be configurable on prod.
So, in addition to what we have today, we need an ability to define configurable settings according to the environment used.
Proposed solution
various options i can think about:
enable defining configurable properties in environment files
enable creating a config file per environment and using it in code like environment with file replace in angular.json like environment
Alternatives considered
currently we can create a "configFile" property in all environments, but all those files are assets, so all of them are deployed during CI\CD although a specific environment has been built.
The text was updated successfully, but these errors were encountered:
Which @angular/* package(s) are relevant/related to the feature request?
No response
Description
There is a nice ability in angular to define multiple environments and have a different build per each of them.
The only problem is that environment file is NOT configurable on prod but there are settings need that ability for us,
for example: "serverApiUrl" which we need to be configurable on prod.
So, in addition to what we have today, we need an ability to define configurable settings according to the environment used.
Proposed solution
various options i can think about:
Alternatives considered
currently we can create a "configFile" property in all environments, but all those files are assets, so all of them are deployed during CI\CD although a specific environment has been built.
The text was updated successfully, but these errors were encountered: