Mercurial > gemma

diff cmd/gemma/gemma.toml.example @ 330:fd04bccae6ca

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Create standard roles as part of the base schema. We will always need: 1. a gemma service user 2. an initial sys_admin user so these are now created as part of the base gemma schema. The install-db script now creates random default passwords for this accounts. As the complexity is sufficiently increased by now I also changed the Quick Start guide to use an configuration file and provided an example file.
author Sascha Wilde <wilde@intevation.de>
date Fri, 03 Aug 2018 13:40:10 +0200
parents
children dabe189369ad
line wrap: on
line diff
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/cmd/gemma/gemma.toml.example	Fri Aug 03 13:40:10 2018 +0200
@@ -0,0 +1,43 @@
+# ----------------------------------------------------------------------
+# Example configuration for gemma back end
+# ----------------------------------------------------------------------
+
+# ----------------------------------------------------------------------
+# Basic Setup:
+
+# Host and port to listen on:
+#host = "localhost"
+#port = "8000"
+
+# Where to find the data of the web client (SPA) to serve:
+web = "./web"
+
+# File to persist session data:
+sessions = "session.data"
+
+# ----------------------------------------------------------------------
+# Database:
+
+# DB connection configuration:
+#dbhost = "localhost"
+#dbname = "gemma"
+#dbport = "5432"
+#dbssl = "prefer"
+
+# Database account to use for service tasks
+# (like password reset):
+service-user = "gemma_service"
+#service-password = "SECRET"
+
+# ----------------------------------------------------------------------
+# Mail setup:
+
+# SMTP connection configuration:
+#mail-host = "localhost"
+#mail-password = "SECRET"
+#mail-port = "464"
+#mail-user = "gemma"
+
+# Client data to use:
+#mail-from = "noreplay@localhost"
+#mail-helo = "localhost"