The docker image can be built by running a docker build with the
Dockerfile located in the
Mandatory environment variables:
UPSTREAM_PWAin the form of
For HTTP, the server will run on default port 80.
If HTTPS is chosen as an upstream, it will run on default port 443.
In the latter case the files
server.crt have to be supplied in the container folder
/etx/nginx (either by volume mapping with
docker run or in the image itself by
If the nginx container is run without further configuration, the default Angular CLI environment properties are not overridden.
Multiple PWA channels can be set up by supplying a YAML configuration listing all domains the PWA should work for.
The first way of supplying a configuration for domains is to add multiple domain configuration nodes and specify properties:
'domain1': channel: channel1 application: app1 features: f1,f2,f3 lang: la_CO theme: name|color
The domain is interpreted as a regular expression.
b2b\..+) as well as top level domains (
.+\.com) can be supplied.
channel property is also mandatory.
All other properties are optional:
Dynamically directing the PWA to different ICM installations can by done by using:
Multiple channels can also be configured via context paths, which re-configure the PWA upstream to use a different
baseHref for each channel.
'domain2': - baseHref: /us channel: channelUS lang: en_US - baseHref: /de channel: channelDE lang: de_DE
The domain has to be supplied, to match all domains use
channel are mandatory.
baseHref must start with
Also note that context path channels have to be supplied as a list.
The first entry is chosen as default channel, if the website is accessed without supplying a channel.
This configuration can be supplied simply by setting the environment variable
Alternatively, the source can be supplied by setting
MULTI_CHANNEL_SOURCE in any supported format by gomplate.
If no environment variables for multi-channel configuration are given, the configuration will fall back to the content of
nginx/multi-channel.yaml, which can also be customized.
⚠️Multi-Channel configuration with context paths does not work in conjunction with service workers
An extended example can be found in the
docker-compose.yml in the project root.
The page speed configuration can also be overridden:
NPSC_ENABLE_FILTERSto a comma-separated list of active Page Speed Filters to override our carefully chosen defaults. Do this at your own risk.
Built-in features can be enabled and disabled:
CACHE=offdisables caching (default
PAGESPEED=offdisables pagespeed optimizations (default
COMPRESSION=offdisables compression (default
DEVICE_DETECTION=offdisables user-agent detection (default
PROMETHEUS=onenables Prometheus metrics exports on port
New features can be supplied in the folder
A file named
<feature>.conf is included if the environment variable
<feature> is set to
yes (checked case in-sensitive).
The feature is disabled otherwise and an optional file
<feature>-off.conf is included in the configuration.
The feature name must be all word-characters (letters, numbers and underscore).
If the cache feature is switched off, all caching for pre-rendered pages is disabled.
If the cache should also be disabled for static resources, the page speed feature has to be switched off as well as it caches optimized images individually.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.