MapProxy Docker Image from the YAGA Development-Team. Adapted by justb4 to latest MP version, small Docker image and extended examples. Find image on Docker Hub.
1.13.2,latest
MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.
See the examples, these use docker-compose, more convenient than docker run commands:
- default - default out-of-the-box example
- standard - mapproxy config with some facilities like GeoPackage tile cache, custom grid etc
The second example should give you a nice starter.
But you can run the container with standard docker:
docker run -v /path/to/mapproxy:/mapproxy -p 8080:8080 yagajs/mapproxyIt is optional, but recommended to add a volume. Within the volume mapproxy get the configuration, or create one automatically. Cached tiles will be stored also into this volume.
The container normally runs in http-socket-mode. If you will not run the image behind a HTTP-Proxy, like Nginx, you can run it in direct http-mode by running:
docker run -v /path/to/mapproxy:/mapproxy -p 8080:8080 yagajs/mapproxy mapproxy httpMAPPROXY_PROCESSESdefault: 4MAPPROXY_THREADSdefault: 2UWSGI_EXTRA_OPTIONSextrauwsgicommandline options e.g."--disable-logging --stats 0.0.0.0:9191", default empty
The image also allows arbitrary commands like seeding:
docker exec -it mapproxy mapproxy-seed -f /mapproxy/mapproxy.yaml -s /mapproxy/seed.yaml --seed myseed1
You can put a mapproxy.yaml into the /docker-entrypoint-initmapproxy.d folder on the image. On startup this will be
used as MapProxy configuration. Attention, this will override an existing configuration in the volume!
Additional you can put shell-scripts, with .sh-suffix in that folder. They get executed on container startup.
You should use the mapproxy user within the container, especially not root!
You can also add extra packages in build args: ADD_DEB_PACKAGES and ADD_PIP_PACKAGES.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
This project is published under ISC License.