docs and dockerfile implementing ignore

parent 4fbd95a6
# directories to be excluded
./www/videos
\ No newline at end of file
FROM python:3.8.4-alpine3.11
RUN apk add nfs-utils
WORKDIR "/opt/leuven"
COPY ./server.py /opt/leuven/server.py
COPY ./www /opt/leuven/www
RUN mkdir -p /opt/leuven/www/videos
WORKDIR "/opt/leuven"
CMD [ "python", "server.py" ]
\ No newline at end of file
......@@ -12,12 +12,17 @@ Deployment
Tour is run from OC, project leuven:
```
#Note that there are some mis-confusion with image names and locations
oc project leuven
docker build -t docker-registry.wur.nl/isric/leuven/leuven-v0-2:latest .
docker push docker-registry.wur.nl/isric/leuven/leuven-v0-2:latest
oc import-image leuven-v0-2
docker build -t docker-registry.wur.nl/isric/leuven/leuven-v0-2 .
docker push docker-registry.wur.nl/isric/leuven/leuven-v0-2
oc import-image leuven:latest
```
The docker image contains a video folder that considerable increases the image size and the time for deployment: `./www/videos` this has been changed into using a pod container that will contain a permanent version of the videos.
Google tour key
---------------
......@@ -41,6 +46,17 @@ The key is used on `index.html` around line 30:
Google tour medatainfo
----------------------
Checking on the network console (browser) we have the [GeoPhotoService.GetMetadata](https://maps.googleapis.com/maps/api/js/GeoPhotoService.GetMetadata?pb=!1m5!1sapiv3!5sUS!11m2!1m1!1b0!2m2!1sen!2sUS!3m3!1m2!1e10!2sAF1QipN8WM2np43B5Ze7P_A3_Ftc_EYPWRYV6BbFWmzl!4m6!1e1!1e2!1e3!1e4!1e8!1e6&callback=_xdc_._vlmdra) url that contains metadata of the tour:
Panoid
------
Panoid is used on `tour.js` to start the tour and then on `leuven_tour.json` to define the icon location. Therefore the icon location on the tour is defined by this specific id. Looking at the tour on a browser the current panoid can be obtain on the console, inspecting object `panorama.location`
```
>> panorama.location
```
Development Notes
-----------------
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment