Skip to content
getgeolens.com
GeoLens Docs

Cloud Deployment Notes

GeoLens self-hosts via Docker Compose. Production deployments commonly migrate the database to a managed PostgreSQL service (RDS, Cloud SQL, DigitalOcean Managed Database), storage to S3-compatible object storage, and cache to a managed Redis-compatible service (ElastiCache, Memorystore). The admin’s job at provisioning time is to wire the corresponding env vars correctly and ensure security-group / firewall rules permit outbound HTTPS to the chosen provider’s endpoints.

Backups in cloud context

Section titled “Backups in cloud context”

The backup story intersects with cloud deployment in two places. First, managed PostgreSQL providers offer their own snapshot facilities (RDS automated backups, Cloud SQL backups, DO Managed Database snapshots) — these are the recommended primary backup mechanism in cloud environments because they exploit storage-layer optimizations the GeoLens backup profile cannot. Second, the GeoLens backup profile is still useful for application-level dumps when you need cross-version portability (e.g., upgrading from PostgreSQL 15 to 16 with logical-format dumps, where a physical snapshot is version-locked).

Combine both: provider snapshots for primary recovery, GeoLens backup profile uploaded to S3 for offsite/cross-version archival. See Backups & restore for the GeoLens-side configuration.

Cloud-specific notes

Section titled “Cloud-specific notes”

TLS termination is typically handled at the load balancer or CDN layer; pick what fits your deployment. Cloud providers offer multiple managed paths: AWS Application Load Balancer with ACM, GCP Cloud Load Balancing, DigitalOcean App Platform’s automatic Let’s Encrypt, or self-managed Caddy/Traefik on a VM.

For the full AWS / GCP / DigitalOcean walkthrough — managed-service setup, env var wiring, DNS configuration, and provider-specific gotchas — see Cloud Deployment (682 lines, provider-organized).

See also

Section titled “See also”