Mercurial > gemma
view README.md @ 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 | d68dfbe768e2 |
children | f62ee9d5bff1 |
line wrap: on
line source
# Quick Start ## Build - To build all components of gemma, simply type `make` on the top level directory of the repro. - To only (re)build the back end you can use `make gemma`. - To only build the SPA-Client you can use `make client`. For further details see [docs/DEVELOPMENT](docs/DEVELOPMENT.md), ## Setup Database - You will need a PostgreSQL cluster with PostGIS. - To install the **gemma** schema and roles use the script `./schema/install-db.sh`. - `./schema/install-db.sh --help` shows you available options. Per default the script will create a database named "gemma" and all necessary roles in the postgres default cluster (listening on port 5432). - The script must be run as a user with PostgreSQL super user rights. By convention this is the "postgres" on most systems. ## Running gemma - Best is to create a configuration file. Copy the example from `example_conf.toml` to get started: ``` cp example_conf.toml gemma.toml ``` - Edit `gemma.toml`, some parameters you probably want to change: * `host` and `port` to make gemma listen on a public interface * `metamorph-db-password` to match the password for your database user * `geoserver-url`, `geoserver-user` and `geoserver-password` to match your instance of GeoServer - `./cmd/gemma/gemma -h` gives you an overview of more available options. - Then start gemma: ``` ./cmd/gemma/gemma ```