view example_conf.toml @ 567:f3452ce5c056

Make table writable for data import Lookup tables will probably be filled with data during import and thus should reside in the waterway schema, which is accordingly authorised. Touch only the one table relevant for bottlenecks here, as other data might be handled differently. Lookup tables referenced in out-commented columns not touched, as it is not yet clarified whether these columns will be removed completely. countries not touched neither, because it will be filled from different source and demo-data should have everything necessary to start importing bottlenecks.
author Tom Gottfried <tom@intevation.de>
date Tue, 04 Sep 2018 21:41:45 +0200
parents 7e45aaec7081
children d11f1211b4e6
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"

# ----------------------------------------------------------------------
# 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"

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

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

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