This is meant to be run on a fresh machine with no previously installed packages or GeoNode versions.
Warning
The methods presented here are meant to be used for a limited internal demo only.
Before exposing your GeoNode instance to a public server, please read carefully the hardening guide
A definite specification of technical requirements is difficult to recommend. Accepted performance is highly subjective. Furthermore, the performance depends on factors such as concurrent users, records in the database or the network connectivity of your infrastructure.
For deployment of GeoNode on a single server, the following are the bare minimum system requirements:
8GB of RAM (16GB or more preferred for a production deployment).
2.2GHz processor with 4 cores. (Additional processing power may be required for multiple concurrent styling renderings)
30 GB software disk usage (Reserved to OS and source code only).
Additional disk space for any data hosted with GeoNode, data stored on the DataBase and tiles cached with GeoWebCache.
For db, spatial data, cached tiles, and “scratch space” useful for administration, a decent baseline size for GeoNode deployments is between 50GB and 100GB.
OSGeoLive is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu,
that allows you to try a wide variety of open source geospatial software without installing anything.
It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around.
It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and
manipulation of data.
It also contains sample datasets and documentation.
To try out the applications, simply:
Insert DVD or USB thumb drive in computer or virtual machine.
Reboot computer. (verify boot device order if necessary)
Press Enter to startup & login.
Select and run applications from the Geospatial menu.
A container image is a lightweight, stand-alone, executable package of a piece of software that includes everything needed to run it: code, runtime, system tools, system libraries, settings.
Docker containers running on a single machine share that machine’s operating system kernel; they start instantly and use less compute and RAM.
Containers can share a single kernel, and the only information that needs to be in a container image is the executable and its package dependencies, which never need to be installed on the host system.
Multiple containers can run on the same machine and share the OS kernel with other containers, each running as isolated processes in user space.
The following tutorials will introduce the use of Docker community edition on:
