Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Use cases:

  • Positioning with DNA Spaces

  • FMF with DNA Spaces

This LIPI server is just a docker-based nginx server that adds some headers. Is is designed to be very simple and require very few or no upgrades over time. It is started by an entrypoint that first downloads config files and ssl certificate from our servers.

Map editor configuration requirements

  • A mazepos.com subdomain DNS entry pointing to the local private IP of the server where the Proxy-LIPI will be running.

  • A network configuration set up that covers the public IP range(s) of the customer that intends to communicate with this LIPI, that points to the dns entry above.

  • A position configuration with type “MM_POSITION_CONFIG_TYPE_CLOUD_POSITIONING”

  • A LIPI Config set up with position provider type “MazeMap Cloud Positioning”, pointing to the position config above and the dns entry above.

Server requirements

No specific requirements except that it should have docker installed. To install docker on various platforms see https://docs.docker.com/get-docker/.

The CPU and RAM requirements will vary on traffic, but in most cases will not have any specific requirements, as this is a simple nginx proxy. E.g. running a minimum of 1x CPU and 2 GB Ram should cover most use cases.

Installation, running and basic usage

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:

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:

docker run --rm --name proxy-lipi \
    --env-file $LIPI_ENV_FILE \
    -p 443:4343 \
    gcr.io/mazemap-public-docker/proxy-lipi:latest

After this, the service should be running and can be accessed from the local network.

This can be tested from the server with:

curl https://localhost:443/health -k

Or from anywhere on the local network with:

curl https://<my-subdomain>.mazepos.com:443/health

To run the container in the background (detached mode):

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:

docker ps -a
docker logs -f <container_id>

Restarting

To restart the container, first remove it:

docker rm -f proxy-lipi

Then start it again as described above.

  • No labels