GeoMoose: Difference between revisions
Brian Wilson (talk | contribs) mNo edit summary |
Brian Wilson (talk | contribs) mNo edit summary |
||
Line 1: | Line 1: | ||
== Overview == | |||
I | I am setting up a demo copy of Geomoose so that I can see how it works internally. | ||
It has two parts, a mapserver and a javascript client. | |||
The official project is now in github, https://github.com/geomoose | |||
There are several repos. See their get started docs at http://geomoose.org | |||
== Docker based Geomoose == | |||
Geomoose 3 ("gm3") uses Docker (in the Linux example anyway) to set up a copy of mapserver. | |||
It includes a build step that takes too long IMO! I copied the Dockerfile into this [http://github.com/brian32768/docker-geomoose github repo] | |||
and hooked it up to autobuild on Docker Hub. | |||
You should be able to start it running for testing with this: | |||
docker run -p 8000:80 --name geomoose_demo brian32768/geomoose:latest | |||
While it is running I can see it (sorry, not currently providing public access) at http://maps.wildsong.biz:8000/ | |||
You might want to try try http://localhost:8000/ | |||
This docker image is not optimal, and I suspect it could be built on either the official or camptocamp base images. | |||
It looks like I should PROBABLY be using docker-compose and running several separate containers to provide services | |||
but as I said, this is just a demo! | |||
=== How to add your own maps and data === | |||
The demo image also pulls demo data in from the official Geomoose repo so that you are ready to go. In real life, | |||
you should use a separate docker volume to hold your data. This means you put everything in a directory on the server | |||
and then tell Docker to make that directory available to the Geomoose container. I will tell you how to do that later. |
Revision as of 18:46, 27 March 2019
Overview
I am setting up a demo copy of Geomoose so that I can see how it works internally. It has two parts, a mapserver and a javascript client.
The official project is now in github, https://github.com/geomoose There are several repos. See their get started docs at http://geomoose.org
Docker based Geomoose
Geomoose 3 ("gm3") uses Docker (in the Linux example anyway) to set up a copy of mapserver. It includes a build step that takes too long IMO! I copied the Dockerfile into this github repo and hooked it up to autobuild on Docker Hub.
You should be able to start it running for testing with this:
docker run -p 8000:80 --name geomoose_demo brian32768/geomoose:latest
While it is running I can see it (sorry, not currently providing public access) at http://maps.wildsong.biz:8000/ You might want to try try http://localhost:8000/
This docker image is not optimal, and I suspect it could be built on either the official or camptocamp base images. It looks like I should PROBABLY be using docker-compose and running several separate containers to provide services but as I said, this is just a demo!
How to add your own maps and data
The demo image also pulls demo data in from the official Geomoose repo so that you are ready to go. In real life, you should use a separate docker volume to hold your data. This means you put everything in a directory on the server and then tell Docker to make that directory available to the Geomoose container. I will tell you how to do that later.