Add support for deployUrl

[SchnWalter]

Why

Currently, the application works properly only on the domain or subdomain root. If it's moved to a subpath, various resources that contain URLs that start with slash (assets paths, window.href "forced-reloads") won't work

What

• Update IEnvironmentConfig.appBaseUrl to use Angular CLI --deployUrl flag when it's properly implemented
  • Locale is not added to --deployUrl flag when using --localize angular/angular-cli#17737
  • --deploy-url will have no effect on the HTML angular/angular-cli#6666

[koekj]

If possible it would also be nice if the deploymentUrl can be made available in the application itself. As for instance I'm using configuration that relates to the deployment url as startng path. Another option would be to use a macro ${angular.deployUrl} in the generation of the code so that it can be replace in run time?

[SchnWalter]

I haven't checked, and it isn't immediately obvious from the standard, but since <a href="#anchor">Anker</a> produces an URL that contains the base, you should be able to use the URL class to retrieve the deployUrl, so a simple wrapper service will probably do the trick.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base

Thanks for mentioning this.

L.E. I just realized that the above won't work unless you take an element from the DOM, see:

https://developer.mozilla.org/en-US/docs/Web/API/Node/baseURI

[koekj]

I;m using two parameters the deploy url and the base-href which I then manipulate in the index.html
I'm using currently @{angular.deployUrl} as deployUrl and then run a script on runtime over .js,.html,.css and .json to replace this macro in the real url
find dist/$APP_NAME \\( -type d -name .git -prune \\) -o -type f \\( -iname '*.css' -o -iname '*.html' -o -iname '*.js' -o -iname '*.json' \\) -print0 | xargs -0 sed -i \"s|@{angular\\.deployUrl}|$APP_DEPLOY_URL|g\" && node dist/$APP_NAME/server/$APP_LANG/main.js --appName=$APP_NAME --baseUrl=$APP_BASE_URL --configFile=$APP_CONFIG_FILE --deployUrl=$APP_DEPLOY_URL --lang=$APP_LANG"
The @{} is used not to interfer with the enviroment ${} (taken principle from spring boot)

As the -- variables are passed on to the server.ts I can use them with providers within my app to retrieve, this enables me to use hardcoded language specific configuration files that are relative to the deploy-url. The deploy-url is passed in the SSR engine with a provider so that I can retrieve it on the server. I'm using transfer states to get the url if the client is booted in the browser.
I can check if I'm on the server by using the isPlatformServer and then try to load the deploy-url with the injector manually.

By using the APP_NAME I can have one script that starts multiple different apps as every app is outputted to dist/<app_name>.

So I hope I made clear why I need the deploy-url and it should be run time available so that I can move my app's under multiple url's without rebuilding.

The only problem which I now have is that I need to start multiple server modules. I'm still trying to find a solution to load a language build within the same server so that I don't need a deployment per language but can use one nodejs server which hosts multiple languages/multiple apps.

[SchnWalter]

I would go with some different translation system that allows you to change the language at runtime, @ngx-translate/core is a good one, but you should probably replace the default pipe, since it does a lot of work during Change Detection. And I think that SSR should work out of the box, just make sure to add the language codes in the URL.

[SchnWalter]

Closing, deployUrl is now deprecated: angular/angular-cli@e95ecb8