This isn't the best fix because we're still using NODE_ENV=development
in a "production" environment. Ideally we would stop doing this.
Right now, the Helm charts are broken because they deploy the backend
straight into Error state.. This change will unbreak them for the
moment.
Specity a Google Analytics Tracking ID in the `app-config.yaml` to
enable Google Analytics tracking.
```
app:
title:
baseUrl:
googleAnalyticsTrackingId: UA-000000-0
```
If the `googleAnalyticsTrackingId` is not supplied, no tracking script
is added to the application and no tracking can occur.
Includes Helm chart changes to allow overriding the GA Tracking ID.
The app-config.yaml file that comes inside the docker image for the
backend contains configuration for the key `scaffolder.azure`. This
automatically enables the use of azure and it is not possible to set its
values to dummy ones because it will fail when it tries to validate
them.
To avoid the backend throwing an exception for this, the charts are
using the "development" mode (via setting NODE_ENV=development).
This means that the app-config.development.yaml file that ships in the
container woud have higher precedence than the app-config.local.yaml
file that the charts tried to create before. For that reason, for now,
they will override the development file.
A better solution would be to ship the docker images with a minimal
app-config.yaml or even without any config. And then have these charts
provide said file.
Add a Dockerfile which can be used to build an image that the helm
charts will use as default. These images require mkdocs and cookiecutter
to be installed (for now) in order to work around the docker requirement
in kubernetes.
David Tuite