* base front production image on official nginx
* build multi-platform docker images
* build message types outside docker
* set docker build context to path
* build message types before running e2e tests
* add build for arm/v7
* remove build for arm/v7
* increase yarn network timeout
* set front port to 80
* add git labels to images
https://github.com/docker/build-push-action/blob/master/UPGRADE.md#tags-with-ref-and-git-labels
* add images input
* Adding back commented code in the Dockerfile (the protobuf message building).
This way, when node-grpc supports ARM64, we can uncomment the code again.
Co-authored-by: David Négrier <d.negrier@thecodingmachine.com>
Co-authored-by: Lukas Hass @lukashass
The ts-proto lib has the huge advantage of producing code the "Typescript" way and not the "Java" way.
In particular, for "oneof" types in protobuf, it is generating "ADT" that can be used to check if we forgot or not to deal with a type.
API_URL is still accepted for BC compatibility of the self-hosted deployments.
This will allow deploying on a single domain, using a reverse proxy that acts on the path.
This however means that the config needs to be changed for all WorkAdventure deployments.
Without this patch, the index.html contains google analytics at
all times, including for people self-hosting it.
This is a problem for privacy reasons, and only people wanting
to have analytics on their instances should be able to enable
them.
This fixes it by making sure the index.html page is templated
to sideload content from ANALYTICS_CODE_PATH (which itself is
also templated, for convenience).
