Skip to content

Integrations

These pages explain the external systems the current backend can connect to once the base install is working.

Read this section after Installer, especially when the installer output names an integration blocker such as gee-probe, gcs-upload-probe, geoserver-probe, or public_api_check.

What changed in the current backend install flow:

  • GEE can now be imported directly during install.sh with --gee-json or --input gee_json=....
  • GeoServer settings can be queued into the installer and are probed during initialisation_check when present.
  • Public API credentials live in nrm_app/.env and can drive the installer-side public_api_check.
  • AWS/S3 is still deployment-specific and is not part of the baseline installer validation.

Use these pages by integration surface:

  • Google Earth Engine for GEEAccount setup, GEE_DEFAULT_ACCOUNT_ID, service-account imports, GCS upload readiness, and compute dependencies.
  • GeoServer for publication, REST validation, public geometry delivery, and workspace-facing behavior.
  • AWS for S3-backed storage variables and deployment-specific upload surfaces.

When the computation itself is already understood, continue into Pipeline Integrations or Add and Integrate Public / New Data Resources.