Skip to main content

Runtime and Admin API

These routes cover service health, configuration, auth, storage cleanup, cache administration, and built-in viewer pages.

Health, Root, and Config

MethodPathPurposeAuth
GET/browser-facing root redirect into the frontend UIno
GET/healthliveness probe for service/container healthno
GET/configexpose effective runtime configurationno
POST/configpersist runtime configuration overridesyes
POST/config/resetreset persisted configuration back to environment defaultsyes
POST/storage/cleanup-tmpclear temporary working files under runtime storageyes

Auth

MethodPathPurposeAuth
POST/tokenissue bearer token using the password-flow formno
POST/loginalias for /token used by Swagger login flowsno

MapCache Administration

MethodPathPurposeAuth
POST/mapcache/reloadregenerate mapcache.xml and trigger reload behavioryes
GET/mapcache/cache/layerslist cache directories and layer usageno
POST/mapcache/cache/layersinspect or create cache-layer bookkeepingyes
POST/mapcache/cache/cleanupremove cached tiles using cleanup filtersyes
POST/mapcache/cache/cleanup-layersdelete entire cache layer directoriesyes

Built-In Viewers and Test Pages

MethodPathPurpose
GET/ui/operator frontend
GET/guide/Docusaurus documentation site
GET/guide/blogblog index for project updates and operational notes
GET/docsSwagger UI
GET/openapi.jsonOpenAPI schema export
GET/ui-react/React operator frontend
GET/maplibre/viewMapLibre viewer page
GET/cesium/helloCesium hello page
GET/cesium/ionCesium Ion example
GET/cesium/wmsCesium WMS viewer
GET/cesium/terrain-testterrain-oriented Cesium test page
GET/cesium/csw-searchCesium-integrated CSW search page
GET/ogc/csw-infoHTML info page for OGC/CSW endpoint discovery

Notes

  • Runtime configuration is layered: environment defaults first, persisted config in /data/server_config.json second.
  • Cache cleanup routes operate on shared on-disk tile state, so use them carefully in multi-user or production-like scenarios.
  • The docs site is served by the same API container as the REST endpoints, which keeps deployment simple and ensures /guide versioning matches the running branch/image.
  • The blog lives under the same mounted docs site, so /guide/blog is part of the same static documentation build.