Switch branches/tags
debian/2.10.0+rc4 debian/2.10.0+rc3 debian/2.10.0+rc2 debian/2.10.0+rc1 debian/2.10.0+rc0 debian/2.8.1+rc0 debian/2.8.0+thefinal0 debian/2.8.0+rc13 debian/2.8.0+rc12 debian/2.8.0+rc11 debian/2.8.0+rc10 debian/2.8.0+rc9 debian/2.8.0+rc8 debian/2.8.0+rc7 debian/2.8.0+rc6 debian/2.8.0+rc5 debian/2.8.0+rc4 debian/2.8.0+rc3 debian/2.8.0+rc2 debian/2.8.0+rc1 debian/2.8.0+rc0 debian/2.7.5+dev20180124154147 debian/2.7.5+dev20180123112419 debian/2.7.4+dev20171114153121 debian/2.7.2+dev20171013181704 debian/2.7.1+dev20171013111656 debian/2.7.0+thefinal0 debian/2.6.3+thefinal0 debian/2.6.2+thefinal0 debian/2.6.1+thefinal0 debian/2.6.0+thefinal0 debian/2.6.0+rc1 debian/2.6.0+beta1 debian/2.6.0+alpha1 debian/2.5.15+thefinal0 debian/2.5.14+thefinal0 debian/2.5.13+thefinal0 debian/2.5.12+thefinal0 debian/2.5.11+thefinal0 debian/2.5.10+thefinal0 debian/2.5.9+thefinal5 debian/2.5.9+thefinal4 debian/2.5.9+thefinal3 debian/2.5.9+thefinal2 debian/2.5.9+thefinal1 debian/2.5.9+thefinal0 debian/2.5.9+dev20170116091118 debian/2.5.7+thefinal0 debian/2.5.6+thefinal0 debian/2.5.5+thefinal0 debian/2.5.4+thefinal0 debian/2.5.3+thefinal0 debian/2.5.2+thefinal0 debian/2.5.1+thefinal0 debian/2.5.0+thefinal0 debian/2.4.1+thefinal1 debian/2.4.0+thefinal0 debian/2.4.0+rc4 debian/2.4.0+rc3 debian/2.4.0+rc2 debian/2.4.0+rc1 debian/2.4.0+dev20141024171719 debian/2.4.0+beta28 debian/2.4.0+beta27 debian/2.4.0+beta26 debian/2.4.0+beta25 debian/2.4.0+beta24 debian/2.4.0+beta23 debian/2.4.0+beta22 debian/2.4.0+beta21 debian/2.4.0+beta20 debian/2.4.0+beta19 debian/2.4.0+beta18 debian/2.4.0+beta17 debian/2.4.0+beta16 debian/2.4.0+beta15 debian/2.4.0+beta14 debian/2.4.0+beta13 debian/2.4.0+beta12 debian/2.4.0+beta11 debian/2.4.0+beta10 debian/2.4.0+beta9 debian/2.4.0+beta8 debian/2.4.0+beta7 debian/2.4.0+beta6 debian/2.4.0+beta5 debian/2.4.0+beta4 debian/2.4.0+beta3 debian/2.4.0+beta2 debian/2.4.0+beta1 debian/2.4.0+alpha38 debian/2.4.0+alpha37 debian/2.4.0+alpha36 debian/2.4.0+alpha35 debian/2.4.0+alpha34 debian/2.4.0+alpha33 debian/2.4.0+alpha32 debian/2.4.0+alpha31 debian/2.4.0+alpha30 debian/2.4.0+alpha29
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
341 lines (214 sloc) 12.2 KB
.. _quick_installation:
Quick Installation Guide
The following is a quick guide to get GeoNode up and running in most common operating systems.
This is meant to be run on a fresh machine with no previously installed packages or GeoNode versions.
Recommended Minimum System Requirements
For deployment of GeoNode on a single server, the following are the *bare minimum* system requirements:
* 6GB of RAM, including swap space.
* 2.2GHz processor. (Additional processing power may be required for multiple concurrent styling renderings)
* 1 GB software disk usage.
* Additional disk space for any data hosted with GeoNode and tiles cached with GeoWebCache.
For spatial data, cached tiles, and "scratch space" useful for administration, a decent baseline size for GeoNode deployments is 100GB.
* 64-bit hardware recommended.
Ubuntu (standard deployment)
The easiest way to get the .deb is to install it using APT, the standard installation management tool for Ubuntu. The current release, 2.8 is available only for Ubuntu 16.04.
These instructions have been tested on a fresh install of Ubuntu 16.04 64 bit server edition. Please ensure the latest packages are installed with::
sudo apt-get update; sudo apt-get upgrade
Amongst other things, this will ensure that the ``software-properties-common`` package is installed, which is required to make the ``add-apt-repository`` command used below available.
The steps to install geonode and all dependencies in Ubuntu 16.04 are as follows:
1. Set up the GeoNode PPA repository (you only need to do this once; the repository will still be available for upgrades later)::
sudo add-apt-repository ppa:geonode/stable
.. note:: If you want to try latest unstable version of GeoNode, add the repository::
sudo add-apt-repository ppa:geonode/testing
2. Install the geonode package and dependencies::
sudo apt-get update; sudo apt-get upgrade; sudo apt-get autoremove
sudo apt-get install geonode
3. Set the correct IP address (NB: the first command below looks up the IP address automatically)::
.. note:: If you want to run geonode on your local instance, just run::
sudo geonode-updateip -p localhost
IP_ADDRESS=$(ip route get | awk '{print $NF; exit}')
sudo geonode-updateip -p $IP_ADDRESS
.. note:: If geoserver and geonode are not on the same machine then add your local geonode address::
sudo geonode-updateip -p $IP_ADDRESS -l yourlocaladdress
NB: The IP address must be set to enable access from another machine, e.g. the host machine if geonode is installed in a virtual machine.
4. Access geonode from your web browser, using the IP address from step 3 above. The neonode web applicaiton should be displayed and you can log in using the superuser details entered immediately above::
.. note:: If you want to access geonode on your local instance, just go to::
NB: With this installation method you use ``sudo geonode xxxx`` in place of any ``python xxx`` command referred to in documentation. For example, try::
sudo geonode help
For further information, read the Admin Docs at
Ubuntu (for development)
This option installs geonode in a virtual environment. This option is very useful in case you want to develop using Ubuntu (tested on Ubuntu 16.04 LTS)::
# Install Ubuntu dependencies
sudo apt-get update
sudo apt-get install python-virtualenv python-dev libxml2 libxml2-dev libxslt1-dev zlib1g-dev libjpeg-dev libpq-dev gdal libgdal-dev git default-jdk
# Install Java 8 (needed by latest GeoServer 2.9)
sudo apt-add-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer
# Create and activate the virtulenv
virtualenv --no-site-packages env
source env/bin/activate
# git clone geonode
git clone
cd geonode
# Install pip dependencies
pip install -r requirements.txt --upgrade
pip install -e . --upgrade --no-cache
sudo add-apt-repository ppa:ubuntugis/ppa && sudo apt-get update
sudo apt-get install gdal-bin
# install the correct PyGDAL version
gdal-config --version | cut -c 1-5 | xargs -I % pip install 'pygdal>=%.0,<=%.999'
# if the command cannot install a suitable version, be sure to install at least the closer major one e.g. 2.1.2 ->
# gdalinfo --version
# pip install pygdal==`gdal-config --version`
You can now setup and start GeoNode::
# Paver setup
paver setup
paver sync
paver start
In case you want to be involved in static files development::
# The following lines must be run only the first time
sudo apt-get install -y nodejs, npm
Rebuild libraries through::
cd geonode/static
# The following lines must be run only the first time
npm install --save-dev
npm install bower --save-dev
npm install grunt-cli --save-dev
npm install grunt-contrib-jshint --save-dev
npm install grunt-contrib-less --save-dev
npm install grunt-contrib-concat --save-dev
npm install grunt-contrib-copy --save-dev
npm install grunt-text-replace --save-dev
npm install grunt-contrib-uglify --save-dev
npm install grunt-contrib-cssmin --save-dev
npm install grunt-contrib-watch --save-dev
npm install -g grunt-cli
# Later you can just do the following
bower cache clean
bower update
grunt production
.. warning::
If you get an error like ``/usr/bin/env: node: No such file or directory`` while running ``bower``, try to execute the following command::
sudo ln -s /usr/bin/nodejs /usr/bin/node
On a production environment, remember to refresh also the "static_root" folder::
python collectstatic --clear -i site-packages* -i .components* -i node_modules* --noinput
Windows, OSX and others
It is now available an automatic installer for Windows systems which configures GeoNode with PostgreSQL DB and few sample layers on a few steps.
See detailed instructions and steps of the GeoNode Windows Installer at section :ref:`win_binary_installer`.
If you have different needs or just want to configure the GeoNode environment manually, please continue reading the guide below.
To install in Windows it is assumed you're familiar with python development and virtualenv on Windows and that you're familiar with the windows command prompt. You will need the follow prerequisites installed:
* Java JDK
* Python 2.7.9
* Earlier versions of python require you to install distutils (easy_install) -
* ant (bin directory must be on system PATH)
* maven2 (bin directory must be on system PATH)
* git
Install and configure from the windows command prompt, if you don't already have python virtualenv installed, then do it now::
easy_install virtualenv
Create virtualenv and activate it::
cd <Directory to install the virtualenv & geonode into>
virtualenv <name of virtualenv folder>
virtualenv <name of virtualenv folder>\scripts\activate
Clone GeoNode::
git clone
cd geonode
Install Python native dependencies, this command will look for and install binary distributions (pip install will attempt to build and fail)::
pip install paver
paver win_install_deps
Install GeoNode in the local virtualenv::
pip install -e . --upgrade --no-cache
You have two options to set up the GEOS and GDAL libraries. Either create an environment variable
or add the variables to your file as below.
The GEOS and GDAL libraries can be found in your <virtualenv directory>\Lib\site-packages\GDAL-1.11.0-py2.7-win32.egg\osgeo\ folder.
Setup GeoServer::
paver setup
Start the servers. You have the option to set the JAVA_HOME environment variable or use the --java_path.::
paver start --java_path="C:\path\to\java\java.exe"
or if you set your JAVA_HOME environment variables (e.g. JAVA_HOME="C:\Program Files\Java\jdk1.7.0_75\")::
paver start
Once the package is installed, please consult :ref:`custom_install` to learn how to create an account for the admin user and tweak the settings to get more performance.
The recommended install method in these platforms is to use a virtualization solution, like `Virtual Box`_, install the latest `Ubuntu Linux`_ and then proceed with the steps mentioned above. Some GeoNode developers prefer to use `Vagrant`_ - a VirtualBox wrapper, the steps for this are detailed below. The Vagrant quickstart guide shows how to get a Linux VM configured in most operating systems. However, if you would like to develop natively on Mac OS X please follow the following instructions.
You may need brew install various dependencies::
mkdir -p ~/pyenv
virtualenv ~/pyenv/geonode
source ~/pyenv/geonode/bin/activate
git clone
cd geonode
pip install lxml
pip install pyproj
pip install nose
pip install httplib2
pip install shapely
pip install pillow
pip install paver
Node and tools required for static files development::
brew install node
npm install -g bower
npm install -g grunt-cli
Rebuild libraries through::
cd geonode/static
bower cache clean
bower update
grunt production
On a production environment, remember to refresh also the "static_root" folder::
python collectstatic --clear -i site-packages* -i .components* -i node_modules* --noinput
Install pip dependencies::
pip install -e . --upgrade --no-cache
Paver handles dependencies for Geonode, first setup (this will download and update your python dependencies - ensure you're in a virtualenv)::
paver setup
paver start
Optional: To generate document thumbnails for PDFs and other ghostscript file types, download ghostscript:
sudo apt-get install imagemagick
brew install imagemagick
pip install Wand==0.3.5
Once fully started, you should see a message indicating the address of your geonode.
The default username and password are ``admin`` and ``admin``::
Development GeoNode is running at http://localhost:8000/
The GeoNode is an unstoppable machine
Press CTRL-C to shut down
Before starting GeoNode (paver start), you could test your installation by running tests::
paver test
paver test_integration
In case you want to build yourself the documentation, you need to install Sphinx and the run 'make html' from within the docs directory::
pip install Sphinx
cd docs
make html
You can eventually generate a pdf containing the whole documentation set. For this purpose, if using Ubuntu 12.4 you will need to install the texlive-full package::
sudo apt-get install texlive-full
make latexpdf
.. note::
When running ``virtualenv venv`` the ``--system-site-packages`` option is
not required. If not enabled, the bootstrap script will sandbox your virtual
environment from any packages that are installed in the system, useful if
you have incompatible versions of libraries such as Django installed
system-wide. On the other hand, most of the times it is useful to use a version of
the Python Imaging Library provided by your operating system
vendor, or packaged other than on PyPI. When in doubt, however, just leave
this option out.
.. _VirtualBox:
.. _Vagrant:
.. _Ubuntu Linux:
CentOS/RHEL and other \*nix distros
We recommend you to download the latest release and modify the included ```` and ``support/``. GeoNode has been installed in CentOS/RHEL using this mechanism.
Once the package is installed, please consult the :ref:`custom_install` to learn how to create the admin user and tweak the settings to get more performance.