UI/Help package tokens do not work for VM installations (v10+) about cli HOT 5 CLOSED

We are exploring if this can be fixed in the DF side or if we need to add a (temporary) feature to the CLI to support both scenarios. However, this will break one of the principles of the packages, being agnostic to installation target.

from cli.

A work around would be to edit the generated package and replacing the tokens with ones supported by the traditional installation process:

config.json

$(TENANT_NAME) -> $(Product.Tenant.Name)
$(APPLICATION_PUBLIC_HTTP_TLS_ENABLED) -> $(Product.ApplicationServer.EnableSsl)
$(APPLICATION_PUBLIC_HTTP_ADDRESS) -> $(Product.ApplicationServer.Address)
$(APPLICATION_PUBLIC_HTTP_PORT) -> $(Product.ApplicationServer.Port)
$(SYSTEM_NAME) -> $(Product.SystemName)
"$(SECURITY_PORTAL_STRATEGY_LOCAL_AD_DEFAULT_DOMAIN) -> $(Product.Security.Domain)

index.html and ngsw.json

replace $(APPLICATION_BASE_HREF) with /

from cli.

This is technically a Deployment Framework bug, not a CLI bug, but I've tagged the issue as such anyway for easier reference.

from cli.

Thanks for your guidance, my page can also be displayed, otherwise I will be stuck in the project

from cli.

This is fixed by MES 10.1, in which VM DF understands the container tokens

from cli.