How impanyu/adma_geonode_adapted works
This repository is a customized GeoNode/Django project template for an agricultural data portal, with ADMA branding and Docker-oriented configuration. The main user workflow is browser access to the Django site, which uses project URL and template customization to present GeoNode’s portal; GeoNode’s geospatial capabilities rely on GeoServer and PostGIS. Celery is registered as an internal asynchronous-work layer. The sampled source shows project setup and integration settings, but not GeoNode’s internal request handlers or data operations, so those links are intentionally high-level.
Main entry points: settings.py Django settings · tasks.py Runtime task configuration · wsgi.py WSGI entry · urls.py Project routes
Components 16
Portal web layer
- WSGI entry
src/adma_geonode_project/wsgi.py - Django settings
src/adma_geonode_project/settings.py - Project routes
src/adma_geonode_project/urls.py - Portal templates
src/adma_geonode_project/templates - Branding assets
src/adma_geonode_project/static - MapStore config
src/adma_geonode_project/templates/geonode-mapstore-client/_geonode_config.html
Geospatial platform
- GeoNode platform
- GeoServer
Data and jobs
- PostGIS databases
- Celery app
src/adma_geonode_project/celeryapp.py - App setup hooks
src/adma_geonode_project/apps.py
Runtime configuration
- Environment generator
create-envfile.py - Runtime task configuration
src/tasks.py - Environment template
.env.sample - Web proxy
Other components
- Portal user
Connections 16
- Portal user → Web proxy: requests portal
- Web proxy → WSGI entry: forwards requests
- WSGI entry → Django settings: loads settings
- Django settings → Project routes: selects routes
- Project routes → GeoNode platform: routes portal requests
- GeoNode platform → Portal templates: renders overrides
- GeoNode platform → Branding assets: serves assets
- GeoNode platform → MapStore config: uses map config
- Django settings → GeoNode platform: extends platform settings
- GeoNode platform → GeoServer: geospatial integration
- GeoNode platform → PostGIS databases: database integration
- App setup hooks → Celery app: registers app
- Celery app → Django settings: loads configuration
- Environment generator → Environment template: fills template
- Runtime task configuration → PostGIS databases: configures database access
- Runtime task configuration → GeoServer: configures service access