Skip to content
A django template project for creating custom GeoNode projects.
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
fixtures - Adding the default "base.menuplaceholder" to fixtures as it is in … Jun 14, 2019
package/support - Adding few misc utils (package support) Oct 23, 2018
project_name Bump GeoServer to 2.15.2 Jul 22, 2019
scripts fix space Jun 13, 2019
.env Move env variables to files Jun 13, 2019
.gitignore - Fix get started link on index page Jun 15, 2019
Dockerfile Fixed Numpy for 1.16 Jul 16, 2019
Makefile Added pull to hardreset Aug 18, 2016
README.rst - 2.10 stable release Jul 10, 2019
dev_config.yml Bump GeoServer to 2.15.2 Jul 22, 2019
docker-compose.development.override.yml [Settings] Restoring /gs to /geoserver by default Jun 3, 2019
docker-compose.development.yml Bump GeoServer to 2.15.2 Jul 22, 2019
docker-compose.override.yml - Lightened docker-compose Jun 3, 2019
docker-compose.yml Bump GeoServer to 2.15.2 Jul 22, 2019 - Lightened docker-compose Jun 3, 2019
jetty-runner.xml sync with upstream on Jan. 2, 2017 Jan 3, 2017 - copyrights to OsGeo Jul 18, 2018 align yaml.load with core Jul 1, 2019
playbook.yml Bump GeoServer to 2.15.2 Jul 22, 2019
requirements.txt [Fixes #86] Error Install Geonode 2.10 Jul 11, 2019 update version and cleanup settings Sep 26, 2018 Correct path to initial_data Jul 14, 2019
uwsgi.ini - Docker optimizations Jun 9, 2019 - Improvements to GeoNode-Project Dokerization / Cleaning up depende… Jul 18, 2018


{{ project_name|title }}

GeoNode template project. Generates a django project with GeoNode support.

Developer Workshop

Available at:

Create a custom project

Note: You can call your geonode project whatever you like following the naming conventions for python packages (generally lower case with underscores (_). In the examples below, replace my_geonode with whatever you would like to name your project.

Using a Python virtual environment

To setup your project using a local python virtual environment, follow these instructions:

  1. Prepare the Environment
git clone -b 2.10.x
mkvirtualenv my_geonode
pip install Django==1.11.21

django-admin startproject --template=./geonode-project -e py,rst,json,yml,ini,env,sample -n Dockerfile my_geonode

cd my_geonode
  1. Setup the Python Dependencies
pip install -r requirements.txt --upgrade
pip install -e . --upgrade

GDAL_VERSION=`gdal-config --version`
PYGDAL_VERSION="$(pip install pygdal==$GDAL_VERSION 2>&1 | grep -oP '(?<=: )(.*)(?=\))' | grep -oh $GDAL_VERSION\.[0-9])"
pip install pygdal==$PYGDAL_VERSION

# Using Default Settings
DJANGO_SETTINGS_MODULE=my_geonode.settings paver reset
DJANGO_SETTINGS_MODULE=my_geonode.settings paver setup
DJANGO_SETTINGS_MODULE=my_geonode.settings paver sync
DJANGO_SETTINGS_MODULE=my_geonode.settings paver start

# Using Custom Local Settings
cp my_geonode/ my_geonode/

vim my_geonode/
--> os.environ.setdefault("DJANGO_SETTINGS_MODULE", "my_geonode.local_settings")

DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver reset
DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver setup
DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver sync
DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver start
  1. Access GeoNode from browser:



default admin user is admin (with pw: admin)

Start your server

You need Docker 1.12 or higher, get the latest stable official release for your platform.

  1. Prepare the Environment
git clone -b 2.10.x
mkvirtualenv my_geonode
pip install Django==1.11.21

django-admin startproject --template=./geonode-project -e py,rst,json,yml,ini,env,sample -n Dockerfile my_geonode

cd my_geonode
  1. Run docker-compose to start it up (get a cup of coffee or tea while you wait)

Remember to update "" in case you are using "local_settings" vim my_geonode/ --> os.environ.setdefault("DJANGO_SETTINGS_MODULE", "my_geonode.local_settings")

docker-compose build --no-cache
docker-compose up -d

before running docker-compose up

  1. Access the site on http://localhost/

If you want to run the instance for development

Use dedicated docker-compose files while developing


In this example we are going to keep localhost as the target IP for GeoNode

docker-compose -f docker-compose.development.yml -f docker-compose.development.override.yml up

How to debug


We are supposing to use IPDB for debugging which is already available as package from the container

  1. Stop the container for the "django" service:
docker-compose stop django
  1. Run the container again with the option for service ports:
docker-compose run -e DOCKER_ENV=development --rm --service-ports django python runserver --settings=my_geonode.settings
  1. Access the site on http://localhost/

If you set an IPDB debug point with import ipdb ; ipdb.set_trace() then you should be facing its console and you can see the django server which is restarting at any change of your code from your local machine.

If you want to run the instance on a public site

Preparation of the image (First time only)


In this example we are going to publish to the public IP http://123.456.789.111

vim docker-compose.override.yml
  --> replace localhost with 123.456.789.111 everywhere

Startup the image

docker-compose up --build -d

To Stop the Docker Images

docker-compose stop

To Fully Wipe-out the Docker Images


This will wipe out all the repositories created until now.


The images must be stopped first

docker system prune -a

Recommended: Track your changes

Step 1. Install Git (for Linux, Mac or Windows).

Step 2. Init git locally and do the first commit:

git init

git add *

git commit -m "Initial Commit"

Step 3. Set up a free account on github or bitbucket and make a copy of the repo there.

Hints: Configuring Requirements.txt

You may want to configure your requirements.txt, if you are using additional or custom versions of python packages. For example:

git+git://<your organization>/geonode.git@<your branch>

Hints: Using Ansible

You will need to use Ansible Role in order to run the playbook.

In order to install and setup Ansible, run the following commands:

sudo apt-get install software-properties-common
sudo apt-add-repository ppa:ansible/ansible
sudo apt-get update
sudo apt-get install ansible

A sample Ansible Role can be found at

To install the default one, run:

sudo ansible-galaxy install GeoNode.geonode

you will find the Ansible files into the ~/.ansible/roles folder. Those must be updated in order to match the GeoNode and GeoServer versions you will need to install.

To run the Ansible playbook use something like this:

ANSIBLE_ROLES_PATH=~.ansible/roles ansible-playbook -e "gs_root_password=<new gs root password>" -e "gs_admin_password=<new gs admin password>" -e "dj_superuser_password=<new django admin password>" -i inventory --limit all playbook.yml


Since this application uses geonode, base source of settings is geonode.settings module. It provides defaults for many items, which are used by geonode. This application has own settings module, {{project_name}}.settings, which includes geonode.settings. It customizes few elements:
  • static/media files locations - they will be collected and stored along with this application files by default. This is useful during development.
  • Adds {{project_name}} to installed applications, updates templates, staticfiles dirs, sets urlconf to {{project_name}}.urls.
Whether you deploy development or production environment, you should create additional settings file. Convention is to make {{project_name}}.local_settings module. It is recommended to use {{project_name}}/ That file contains small subset of settings for edition. It should:
  • not be versioned along with application (because changes you make for your private deployment may become public),
  • have customized at least DATABASES, SECRET_KEY and SITEURL.

You can add more settings there, note however, some settings (notably DEBUG_STATIC, EMAIL_ENABLE, *_ROOT, and few others) can be used by other settings, or as condition values, which change other settings. For example, EMAIL_ENABLE defined in geonode.settings enables whole email handling block, so if you disable it in your local_settings, derived settings will be preserved. You should carefully check if additional settings you change don't trigger other settings.

To illustrate whole concept of chained settings:

|  GeoNode configuration |             |   Your application default    |             |  (optionally) Your deployment(s) |
|                        |             |        configuration          |             |                                  |
|                        | included by |                               | included by |                                  |
|   geonode.settings     |     ->      |  {{project_name}}.settings    |      ->     |  {{project_name}}.local_settings |
You can’t perform that action at this time.