Angular Web Portal Deployment Strategy - Transport Packages vs. Environment-specific Builds

Hello,

I am looking for help on the best deployment approach for our customized AngularWebPortal across multiple environments.

Current Setup:

  • 3 environments: Production, Test, and Development (all running version 9.3.1)
  • Each environment has different URLs for the ApiServer

Desired Workflow: We'd like to deploy the AngularWebPortal using Softwareloader on Dev, then transport it from Dev → Test → Production using transport packages.

The Problem: Each environment requires different configurations in and environment.production.ts files (different URLs). Transport packages don't allow us to modify these environment-specific settings between stages.

Current Workflow: Deploy via Softwareloader with environment-adjusted builds for each stage separately

Question: Is there a way to reach the desired Workflow, or do we have to stick with individual builds and deployments per environment?
How does the ootb Web Portal handle different URLs for different environments?


Thanks in advance for any help.