How georchestra/docker works
1. This repository is not the geOrchestra application code itself; it is the Docker-based orchestration layer for a full geOrchestra SDI stack. Its main job is to define which services run together, how they connect, what data they persist, and how the platform is exposed locally or in production-like environments.
2. The center of the repo is the Compose topology: docker-compose.yml defines the core geOrchestra stack, while docker-compose.override.yml and the extra compose files add optional or auxiliary capabilities. The README explicitly treats these files as the architectural contract for service composition, networking, and volume wiring.
3. The primary ingress path is a reverse-proxy/front door based on Caddy in resources/caddy. External browser traffic comes in through the public FQDN (default georchestra-127-0-0-1.nip.io), terminates TLS at Caddy, and is then routed to internal geOrchestra services. Caddy can use an internal cert for local dev or a real certificate from resources/ssl.
4. The core application boundary is the geOrchestra platform itself: a set of containerized webapps and backend services such as the security proxy and other geOrchestra modules. The README highlights that the base composition includes “all geOrchestra modules,” with services linked through Docker networking rather than exposed directly.
5. Identity and access are backed by LDAP and a database layer. The repo includes dedicated environment files for LDAP and multiple databases, which indicates that authentication/authorization and directory data are separated from the application containers. The security proxy is a key integration point between incoming requests and those identity services.
6. Search/indexing and analytics are handled by Elasticsearch, with an optional Kibana stack configured under resources/kibana. The README notes that Elasticsearch currently has no persistent volume in this composition, so indexes are ephemeral unless changed. Kibana is optional and is integrated into the GeoNetwork admin UI for dashboards/statistics.
7. Messaging and background interaction are present through RabbitMQ, with a dedicated .envs-rabbitmq file. While the README doesn’t spell out every consumer, this is a clear boundary for async communication between modules that need queue-based integration instead of direct synchronous calls.
8. Data management is split between application state and shared geodata. A named GeoServer data volume (geoserver_geodata) is exposed for file upload via SSH/rsync, and those files are mounted into the GeoServer container at runtime. This makes geodata a distinct storage plane from the container images and application configs.
9. Email is intentionally trapped inside the stack for development and QA. The override composition adds SMTP and webmail services so platform-generated emails, such as password reset messages, are delivered to a local mailbox rather than the public internet. That creates a closed-loop outbound mail path for testing.
10. Optional modules are separated into additive compose overlays: docker-compose.gwc.yml for a standalone GeoWebCache and docker-compose.atlas.yml for the Atlas module. The README explicitly says these are not part of the default “core” stack, so diagram them as optional branches rather than always-on dependencies.
11. Configuration is split between env files, the config/ directory, and a secrets/ directory. The env files are grouped by concern (common, database, hosts, ldap, rabbitmq, elastic), while secrets/slapd_password.txt shows that some credentials are meant to be injected from files rather than embedded in compose definitions.
12. The resources/ directory holds supporting runtime assets rather than application code: Caddy config, Kibana config, static files, and SSL material. This repo therefore has a clear boundary between infrastructure configuration and the actual geOrchestra software images, which are pulled from Docker Hub and built upstream.
13. For developers, the repo is designed to be combined with the main geOrchestra source tree and rebuilt images from that codebase. The provided scripts (run.sh, run-datafeeder-gmail.sh) and README instructions show that this repo is primarily for local orchestration, debugging, and deployment validation, not for implementing business logic.
14. In an architecture diagram, the most important flows are: browser → Caddy/TLS → security proxy / geOrchestra webapps; webapps → LDAP/database/Elasticsearch/RabbitMQ; GeoServer ↔ shared geodata volume; platform → local SMTP/webmail; and optional Kibana/GeoWebCache/Atlas added through separate compose overlays.
Main entry points: docker-compose.yml Core Compose · docker-compose.override.yml Override · resources Resources · Caddyfile Caddy Front Door
Components 21
Orchestration
Compose files and scripts that define how the stack is assembled and run.
- Core Compose · Primary service topology for the geOrchestra stack.
docker-compose.yml - Override · Local/dev overrides and auxiliary services.
docker-compose.override.yml - Run Script · Entry point for bringing up the stack in a standard local workflow.
run.sh - Mail Run Script · Specialized run script for the datafeeder/gmail scenario.
run-datafeeder-gmail.sh
Runtime Stack
Core platform services and shared backend dependencies.
- Caddy Front Door · Public ingress, TLS termination, and request routing to internal services.
resources/caddy/etc/Caddyfile - geOrchestra Apps · Core containerized geOrchestra modules served behind the proxy.
docker-compose.yml - Security Proxy · Request boundary that mediates access to protected services.
docker-compose.yml - LDAP · User and group directory backing authentication and authorization.
.envs-ldap - Database · Persistent application database layer for geOrchestra services.
.envs-database-georchestra - Elasticsearch · Indexing and search backend used by platform services.
.envs-elastic - RabbitMQ · Async messaging boundary for background and cross-service interaction.
.envs-rabbitmq - GeoServer · Spatial data service with mounted shared geodata.
docker-compose.yml - Geodata Volume · Named volume holding GeoServer data uploaded via SSH/rsync.
docker-compose.yml - Local SMTP · Closed-loop mail delivery for development and QA.
docker-compose.override.yml - Webmail · Mailbox interface for inspecting platform-generated emails locally.
docker-compose.override.yml
Optional Add-ons
Overlay stacks enabled only for specific use cases.
- Kibana · Optional dashboards and statistics UI for Elasticsearch data.
resources/kibana/kibana.yml - GeoWebCache · Optional standalone cache layer enabled through a separate compose file.
docker-compose.gwc.yml - Atlas · Optional geOrchestra add-on enabled through a dedicated compose overlay.
docker-compose.atlas.yml
Support Assets
Runtime configuration, secrets, and static assets used by containers.
- Config Files · Environment files and config directory used to parameterize services.
config - Secrets · File-injected credentials such as the LDAP password.
secrets/slapd_password.txt - Resources · Caddy, Kibana, SSL, and static assets mounted into containers.
resources
Connections 28
- Run Script → Core Compose: starts · Standard startup path invokes the core compose stack.
- Mail Run Script → Override: starts · Specialized workflow brings up the datafeeder/mail override.
- Core Compose → Caddy Front Door: includes · Defines the public ingress proxy as part of the stack.
- Core Compose → geOrchestra Apps: includes · Defines the main geOrchestra application services.
- Core Compose → Security Proxy: includes · Includes the security boundary in front of protected services.
- Core Compose → GeoServer: includes · Runs GeoServer as a core service.
- Core Compose → LDAP: connects to · Uses LDAP for identity and directory lookups.
- Core Compose → Database: connects to · Uses the relational database for persistent state.
- Core Compose → Elasticsearch: connects to · Uses Elasticsearch for search and indexing.
- Core Compose → RabbitMQ: connects to · Uses RabbitMQ for asynchronous integration.
- Core Compose → Config Files: reads · Loads environment and config values from repo-managed files.
- Core Compose → Secrets: reads · Injects sensitive values from secret files.
- Core Compose → Resources: mounts · Mounts supporting runtime assets into containers.
- Caddy Front Door → Security Proxy: routes to · Forwards browser traffic to internal application gateways.
- Security Proxy → LDAP: authenticates against · Checks user identity and authorization data.
- geOrchestra Apps → Database: persists to · Stores application state in the database layer.
- geOrchestra Apps → Elasticsearch: indexes in · Writes searchable content and metadata.
- geOrchestra Apps → RabbitMQ: publishes to · Uses queues for background and cross-service work.
- GeoServer → Geodata Volume: mounts · Reads and writes shared geodata from the named volume.
- geOrchestra Apps → Local SMTP: sends mail to · Platform-generated mail is trapped in the local SMTP service.
- Local SMTP → Webmail: delivers to · Mail can be inspected through the local webmail UI.
- Override → Local SMTP: adds · Override composition enables local mail services.
- Override → Webmail: adds · Override composition enables mailbox inspection UI.
- Core Compose → Kibana: optionally extends · Kibana is an optional analytics companion for Elasticsearch.
- Core Compose → GeoWebCache: optionally extends · GeoWebCache is enabled through a separate overlay.
- Core Compose → Atlas: optionally extends · Atlas is enabled through a separate overlay.
- Resources → Caddy Front Door: provides config · Supplies Caddy configuration and TLS material.
- Resources → Kibana: provides config · Supplies Kibana runtime configuration.