How rural-environmental-registry/rer-core works
RER is a deployable rural environmental registry: users access the web application, authenticate, submit property information, and use spatial and environmental-calculation services. The repository primarily contains deployment configuration, so the graph follows the README’s documented service topology and capabilities; internal request handling and several service-to-service details are not evidenced by sampled application source.
Main entry points: Gateway API gateway · nginx.conf.template Nginx proxy · Calculation-Engine Calculation engine · Core-Frontend Core frontend
Components 14
User entry
- Nginx proxy
config/Main/nginx/nginx.conf.template - Core frontend
config/Core-Frontend
Registry services
- API gateway
config/Gateway - Core backend
config/Core-Backend - Core PostGIS
config/Core-Backend
Identity services
- Auth frontend
config/Authentication/frontend - Auth backend
config/Authentication/backend - Keycloak
config/Authentication - Auth database
config/Authentication
Spatial and calculation services
- GeoServer
config/Geoserver - Calculation engine
config/Calculation-Engine - Engine database
config/Calculation-Engine - Spatial calculator DB
config/Calculation-Engine
Other components
- Registry user
Connections 14
- Registry user → Nginx proxy: opens application
- Nginx proxy → Core frontend: serves frontend
- Nginx proxy → API gateway: routes API
- Core frontend → API gateway: calls API
- API gateway → Core backend: routes requests
- Core backend → Core PostGIS: reads and writes
- API gateway → Auth frontend: routes requests
- API gateway → Auth backend: routes requests
- API gateway → Keycloak: relays authentication
- Keycloak → Auth database: stores identity data
- Nginx proxy → GeoServer: routes map requests
- API gateway → Calculation engine: routes requests
- Calculation engine → Engine database: uses engine data
- Calculation engine → Spatial calculator DB: uses spatial data