TODO General description

Deployment

Docker

This demo could be deployed using docker. The docker image will be just a nginx base image with the html static built using webpack.

demos/mobbscan-gateway-web
...
├── config
│   ├── default.conf
│   └── nginx.conf
├── docker
│   ├── Dockerfile
│   ├── Dockerfile_builder
│   └── Dockerfile_nginx
...

To build the docker image please execute either of these commands:

# from the *monorepo" base folder...
docker build --build-arg ENVIRONMENT=prod -f demos/mobbscan-gateway-web/docker/Dockerfile -t com.mobbeel/mobbscan-gateway-web-demo:x.y.z .

# from the demos/mobbscan-gateway-web folder...
docker build --build-arg ENVIRONMENT=prod -f docker/Dockerfile -t com.mobbeel/mobbscan-gateway-web-demo:x.y.z ../../

# from the docker folder folder...
docker build --build-arg ENVIRONMENT=prod -f Dockerfile -t com.mobbeel/mobbscan-gateway-web-demo:x.y.z ../../../

There are a couple of reasons to execute the docker build as previously mentioned:

• The app requires all dependencies of the monorepo to be installed. That requires that the multi-stage docker image has access whole "build context" of the project. Check out the code of the demos/mobbscan-gateway-web/docker/Dockerfile
• Once the project is integrated with the CI/CD pipeline, this will be done automatically and it is probably easier if all commands are execute it from the base folder (we would have to come up with a solution to select what to execute for the monorepo approach)

Also, there are 3 environments: dev, stage and production, but this has to be review because it does not make much sense right now.

Runnind the demo with docker

Either pull the latest image available from the docker registry or build it yourself following the previous section.

To run the image locally:

docker run --rm -d -p 80:80 registry.mobbeel.com/com.mobbeel/mobbscan-gateway-web-demo:x.y.z

Open a browser pointing to localhost and the redirections configured on demos/mobbscan-gateway-web/config/default.conf should redirect you to the landing page.

Please be aware that the demo is currently configured to be deployed on a /gateway/ path instead of /. This would be improved on the future so it can be configured dinamically while building the image (actually when compiling the static html code).