mapstory-geonode

[Clarify: mapstory-geonode relation to mapstory meta-project - why isnt the build in the meta-project? if mapstory-geonode handles all the dependencies why do we need the meta-project at all? ]

Repositories

The full build lives in a 'meta-project' at https://github.com/MapStory/mapstory/tree/master. This is used for stability as the upstream dependent projects are pegged to specific versions. While MapStory has forks of upstream projects, the goal is to support temporary efforts that are intended for eventual merging into the respective projects. The forks will be updated as needed.

Deployment

local developer build

clone the following repositories as siblings of each other:

• https://github.com/MapStory/MapLoom
• https://github.com/GeoNode/geonode
• https://github.com/MapStory/geoserver-geonode-ext
• https://github.com/terranodo/storyscapes
• https://github.com/ischneider/geotools (optional - only needed for extended datetime support)

Setup

Follow installation instructions in GeoNode for the relevant operating system. STOP when you reach the point of running pip install -e geonode

Make virtualenv for mapstory, activate it, change directory to mapstory-geonode and run:

pip install -r requirements.txt

NOTE: while it is safer (to avoid conflicts with other packages and keep dependencies isolated) to create your virtualenv using the default mode of ignoring site-packages, this may result in more requirements being installed by pip. It is possible to use the virtualenv flag --system-site-packages if you run into issues.

This is incompatible with the vagrantfile - which is configured to assume a clone of the mapstory meta-project.

If one was to work on a module - and fork it - then how do you work with the fork in the context of the vagrant approach?

• https://github.com/ischneider/geotools (optional - only needed for extended datetime support)

check this last one - what is the status of this and what does it mean in practice?

a manual build process is described in manual_setup.md

an automated virtual machine provisioning process using vagrant is documented in scripts/provision/README.md

Production deployment:

Todo