Enhance clause Using Demo4 with AdvantEDGE

- Create a sandbox & deploy Demo4 scenario

- Start Demo4 application frontend in browser

## Using Demo4 with ETSI MEC Sandbox

#### Build from source

To build demo4-ue & onboarded-demo4 from source code:

```sh

$ cd ~/AdvantEDGE/examples/demo4-ue 

$ ./build-demo4-ue.sh --rebuild_dai

```

NOTE: Binary files are created in ./bin/ folder

#### Dockerize demo applications

Demo Application binaries must be dockerized (containerized) as container images in the Docker registry. This step is necessary every time the demo binaries are updated.

NOTE: Make sure you have deployed the AdvantEDGE dependencies (e.g. docker registry) before dockerizing the demo binaries.

To generate docker images from demo binary files:

```sh

$ cd ~/AdvantEDGE/examples/demo4-ue

$ ./dockerize.sh

```

### Using Demo4 with ETSI MEC Sandbox

To use Demo4 as an external application that interacts with the ETSI MEC Sandbox

- Build Demo4 server & frontend

- Log in to the [ETSI MEC Sandbox](https://try-mec.etsi.org)

- Deploy either of the dual-mep scenarios

- Configure Demo4 application instances

- Start Demo4 application instances

- Demo4 does not have prior knowledge or configuration information of the MEC services offered by the MEC platform.

Therefore, the following steps need to be done prior to running Demo4 application instances.

#### Obtain demo binaries

Use the same procedure described above for Demo4 with AdvantEDGE.

#### Create work directory for demo4-ue instance

Create work directories of your choice on the system of your choosing; we’ll use ~/demo4 for this example.

TODO

The structure should look like this: