Mercurial > gemma
view example_conf.toml @ 2377:fdec7a652f34
client: imports: avoid error when cron string cannot be parsed when trying to edit imports
To prefill the form fields that generate the cron string, the currently stored cron string needs to be parsed back.
This parsing only handles numerical values for each of the six cron fields. In case of something like */15 the
regular expression does not match, leading to a null value. The cronMode select now has an empty option for cases
where the cronString does not match any known pattern.
author | Markus Kottlaender <markus@intevation.de> |
---|---|
date | Fri, 22 Feb 2019 12:28:14 +0100 |
parents | 783c1454ab47 |
children | 0db742c7813d |
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" # 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"