Skip to main content
Version: 1.x

Back-end

The be-config exposes the endpoints used to configure the fe-container:

  • the /authentication endpoint which receives GET requests and responds with the user configuration in JSON format;
  • the /configuration endpoint which receives GET requests and responds with the micro-lc configuration in JSON format;
  • the /configuration/:configurationName endpoint, for which we suggest to read the dedicated section.

Both are written using Node.js and Fastify, with the support of Mia service Node.js library.

Configurations loading​

The configuration returned by each endpoint is read from a JSON file that must be accessible from the be-config instance.

The path where each JSON is stored can be configured using the following environment variables:

  • AUTHENTICATION_CONFIGURATION_PATH, for authentication;
  • MICROLC_CONFIGURATION_PATH, for core.
info

be-config is available as Docker image: using docker run the JSON files can be mounted as volumes. On Kubernetes the JSON files can be inserted in a ConfigMap.