Mercurial > gemma
view README.md @ 467:73c7b2d6246e
Used hex-encoded usernames and a stored procedure to decode them to impersonate with the metamorph user.
author | Sascha L. Teichmann <sascha.teichmann@intevation.de> |
---|---|
date | Wed, 22 Aug 2018 17:43:30 +0200 |
parents | 827103f35006 |
children | fce16726f51d |
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 `cmd/gemma/gemma.toml.example` to get started: ``` cp cmd/gemma/gemma.toml.example gemma.toml ``` - Edit `gemma.toml`, some parameters you probably want to change: * `host` and `port` to make gemma listen on a public interface * `service-password` to match the password for "gemma_service" user of your database. - `./cmd/gemma/gemma -h` gives you an overview of more available options. - Then start gemma: ``` ```