Pavement.py and Paver¶
Paver is a python module that automates repetitive tasks like running documentation generators, moving files around,
testing and downloading things using the convenience of Python’s syntax and massive library of code. GeoNode comes with several
paver tasks which save administrators and developers from having to manually perform repetitive operations from the command line.
The tasks are stored in the pavement.py file in your GeoNode root directory and can be run with `paver <task_name>`
from that directory.
Pavement Tasks¶
Here’s a list of Pavement tasks maintained by the GeoNode development team.
deb¶
`paver deb`
Creates Debian packages.
Use the key
option (or its shorter version -k
) to specify the GPG key to sign the package with.
Use the ppa
option (or its shorter version -p
) to specify the PPA the package should be published to.
reset¶
`paver reset`
Resets the GeoNode development environment by deleting the development database and re-deploying the GeoServer data directory.
reset_hard¶
`paver reset_hard`
Cleans the local GeoNode git repository and removes untracked directories.
setup_data¶
`paver setup_data`
Loads sample GIS data from the gisdata python package.
Use the type
option (or its shorter version -t
) to only import a specific data type. Supported types are “vector”, “raster”, and “time.”
setup_geoserver¶
`paver setup_geoserver`
Downloads GeoServer and the Jetty Runner and then moves the GeoServer data directory to the correct location.
start_django¶
`paver start_django`
Starts the GeoNode development web server on the local machine.
Use the bind
option (or its shorter version -b
) to bind the development server to a specific IP address and port number.
sync¶
`paver sync`
Synchronizes the database according the GeoNode models and loads the GeoNode sample data.
static¶
`paver static`
Note
This task requires the Node Package Manager to be installed.
Downloads and installs GeoNode’s static file dependencies and creates the production assets.
upgrade_db¶
`paver upgrade_db`
Updates database schemas from legacy GeoNode versions.
Use the version
option (or its shorter version -v
) to specify the GeoNode version when running this task.