This package contains the HTTP server to run a MC application in production.
This server should only be used for production, for development we use
@commercetools-frontend/mc-scriptsto start a development server.
$ npm install --save @commercetools-frontend/mc-http-server
We also provide a docker image to run the server:
$ docker run -p 3001:3001 eu.gcr.io/ct-images/mc-http-server:v0.0.0 mc-http-server --config="$(pwd)/env.json"
Why do we need an HTTP Server?
Since a SPA consists of mainly JS bundles and CSS, it's usually not necessary to have an actual HTTP server running. In theory it's enough to serve a static HTML page from e.g. a CDN.
However our MC SPA requires certain information and configuration which cannot be provided on compile time ([*][#inject-variables-at-compile-time]).
This information is available at runtime through environment variables, which needs to by dynamically injected into the
For that reason, before the server starts, we pull the
index.html.template generated on build time (containing references to the JS bundles and placeholders for runtime variables to be injected) and generate the final
All static assets are served from the
Besides generating and serving the
index.html, the HTTP server does additionally a couple of things:
- provides a
/versionendpoint with the current revision hash (git SHA)