One of the useful architectural choices in this repository is that the docs are published with the application image instead of being treated as a separate service.
That keeps the public guide version aligned with the code and deployment that operators are actually running.
The second day focused on confidence: more route-level tests, better job coverage, and a cleaner split between unit validation and runtime smoke checks.
Use a {/* truncate */} comment to limit blog post size in the list view.
The first pass over the Docusaurus site was about removing generic scaffold content and making the docs reflect the actual FastAPI-mapserver deployment and runtime model.
FastAPI-mapserver is the service layer that ties together raster ingestion, OGC publishing, background processing, caching, terrain generation, and HySpex catalog workflows in one operational stack.
This project is not just a FastAPI wrapper around a few endpoints. It is the control plane around GeoTIFF datasets, MapServer and MapCache, Celery workers, Redis-backed job state, a built-in frontend, and terrain products that need to stay aligned across API, storage, and deployment.