Use cases:
...
You need the API key associated with the LIPI config mentioned above. It's good practice to not expose secrets in the command line, so create a file to keep it in that is not readable to other users:
| Code Block |
|---|
export LIPI_ENV_FILE=proxy-lipi-docker-env-file echo "LIPI_API_KEY=" >$LIPI_ENV_FILE chmod 600 $LIPI_ENV_FILE editor $LIPI_ENV_FILE |
In the editor, paste the API key after the equals sign.
Then run:
| Code Block |
|---|
sudo docker run --rm --name proxy-lipi \
--env-file $LIPI_ENV_FILE \
-p 443:4343 \
gcr.io/mazemap-public-docker/proxy-lipi:latest |
| Info |
|---|
Note that this starts the service in the foreground, so you can’t log out without stopping it. This is suitable when testing, but not for production. See below for instructions on how to start the service in the background. |
After this, the service should be running and can be accessed from the local network.
...
To run the container in the background (detached mode):
| Code Block |
|---|
sudo docker run -d --name proxy-lipi \
--env-file $LIPI_ENV_FILE \
-p 443:4343 \
gcr.io/mazemap-public-docker/proxy-lipi:latest |
To access logs, run:
| Code Block |
|---|
sudo docker ps -a sudo docker logs -f <container_id> |
Restarting
If changes have been made to the LIPI config, you might need to restart the proxy-lipi. Changes to these settings require a restart to take effect:
LIPI API key
mazepos subdomain
resolver config
cloud positioning service hostname or port
MazeMap App Id or Key
Turning on or off SSL (https) for testing purposes.
Also if a new version of proxy-lipi has been released, a restart is required.
To restart the container, first remove it:
| Code Block |
|---|
sudo docker rm -f proxy-lipi |
If you want to upgrade, pull the newest version of the image:
| Code Block |
|---|
sudo docker pull gcr.io/mazemap-public-docker/proxy-lipi:latest |
Then start it again as described above.
LIPI-CISCO (DNA) SPACES DIAGRAM
