view example_conf.toml @ 3547:47c61ea894b1

client: map layers: share same vector source object for layers that use the same geoserver view (bottlenecks_geoserver) The layers Bottlenecks, Critical Bottlenecks and Bottlenecks Fairway Availability used the exact same geoserver_view/data. Thus the vector source object can be shared to avoid multiple identical requests. Unfortunately this does not work across maps. So each map has it's own vector source object for the three bottleneck layers.
author Markus Kottlaender <markus@intevation.de>
date Fri, 31 May 2019 12:20:08 +0200
parents d68d8b137072
children 9114097964d7
line wrap: on
line source

# ----------------------------------------------------------------------
# Example configuration for gemma back end
# ----------------------------------------------------------------------

# ----------------------------------------------------------------------
# Basic Setup:

# Host and port to listen on:
host = "0.0.0.0"
#port = 8000

# Where to find the data of the web client (SPA) to serve:
web = "./web"

# File to persist session data:
sessions = "/tmp/gemma_session.data"

# Duration until sessions expire if not renewed
#session-timeout = "3h"

# ----------------------------------------------------------------------
# Database:

# DB connection configuration:
db-host = "gemma-db"
#db-name = "gemma"
#db-port = 5432
#db-ssl = "prefer"
db-user = "meta_login"
db-password = "geo2Serv"

# ----------------------------------------------------------------------
# Mail setup:

# SMTP connection configuration:
#mail-host = "localhost"
#mail-password = "SECRET"
#mail-port = 465
#mail-user = "gemma"

# Client data to use:
#mail-from = "noreplay@localhost"
#mail-helo = "localhost"

# ----------------------------------------------------------------------
# OGC services setup:

# Connection to GeoServer instance for internal OGC services
geoserver-url = "http://gemma-geoserver:8080/geoserver"
#geoserver-user = "admin"
#geoserver-password = "geoserver"

# Clean GeoServer setup on startup
# Persisting this is mainly useful in some dev setups.
# Cleaning up the GeoServer should be done with
# an explicit --geoserver-clean on the command line.
#geoserver-clean = true

# Proxy settings for external OGC services
#proxy-key = "SECRET"
#proxy-prefix = "http://localhost:8000"
#

# Server is known on the outside as:
# external-url = "http://localhost:8000"

# ----------------------------------------------------------------------
# CORS setup:

#allowed-origins = "http://example.com"

# -----------------------
# Schema for "Testclient imports"
# schema-dirs = "$PATH_TO_SCHEMATA"
# published-config ="$PATH/pub-config.json"