| Table of Contents |
|---|
| Note |
|---|
To avoid wasting our own and our customer’s timeinvesting a lot of effort into this only to realize that there’s a requirement that can’t be satisfied, make sure you verify early in the process that all the below requirements are satisfied early in the process. In particular we’ve had problems with customers not realizing that their setup and policies fails the no-NAT requirement, described below. |
...
This LIPI server is just a docker-based nginx server that adds some headers. It 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
| Info |
|---|
Your customer success contact will help you fulfill these 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.
...
| Note |
|---|
Make sure this requirement is cleared with someone who knows what they’re talking about. Ask your local networking guru early in the process. |
Installation, running and basic usage
...
| Code Block |
|---|
sudo docker run --rm --name proxy-lipi \
--env-file proxy-lipi-docker-env-file \
-p 443:4343 \
gcr.io/mazemap-public-docker/proxy-lipi:latest |
| Note |
|---|
Note that this starts the service in the foreground, so you can’t log out or run a different command without stopping it with ctrl+c. This is suitable when testing, but not for production. See below for instructions on how to start the service in the background. |
If the operating system on which proxy-lipi is being installed has https proxy, then run with additional proxy arguments as follows by replacing <https_proxy_domain_here> with https proxy domain
| Code Block |
|---|
sudo docker run --rm --name proxy-lipi \
--env-file proxy-lipi-docker-env-file \
-p 443:4343 \
-e use_proxy -e https_proxy=<https_proxy_domain_here> \
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. |
You should see two messages about connecting to admin.mazemap.com. After this, the service should be running and can be accessed from the local network. This can be tested from the server with:
...