...
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.
Prerequisites:
Docker license if required.
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 (note: that also entails the public IP range from which the LIPI is going to be installed).
A position configuration with type “MM_POSITION_CONFIG_TYPE_CLOUD_POSITIONING”. Details are here /wiki/spaces/DPD/pages/776142882
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.
Local network and WiFi setup requirements
The local network topology needs to be such that the source IP address of the packets received by the Proxy-LIPI server corresponds with the local IP address of that same client in Cisco Spaces.
...
| Note |
|---|
Ensure this requirement is reviewed by your IT department, specifically someone with expertise in network configuration, early in the process to avoid potential issues. |
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 that is not readable to other users:
...
| Code Block |
|---|
curl https://<my-subdomain>.mazepos.com:443/health |
Running in production
Run the container in the background by adding -d or --detached (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 |
...
| Code Block |
|---|
sudo docker ps -a sudo docker logs -f <container_id> |
Upgrading, Restarting, and Maintenance
There can be many reasons why you want to restart the container. When it starts, it downloads a certificate and a configuration associated with your LIPI API key, and if any of those have changed, you need to restart in order to see the effects of those changes. Changes to these things require a restart to take effect:
...
If you want to minimize downtime, put these commands after each other in a script file that you can then run.
LIPI-Cisco Spaces diagram
FAQ
| Info |
|---|
Q: Do we need a static NAT so that MAZEMAP can communicate with it ? Specifically this would be required if we require inbound access rules on the Firewall not just outbound. A: We do not need inbound access. |
...