Mercurial > gemma
view README.md @ 528:076996a41c31
fix: Dockerfile.geoserv - adding "universe" to sources.list
Adding universe to every line of sources.list leads with vanilla images to problems.
https://wiki.ubuntuusers.de/sources.list/#Bionic
There are empty lines, which would contain "universe".
Adding "universe" at the end of lines containing "deb" at the beginning does the trick.
The solution is valued as "good enough" for now.
author | Thomas Junk <thomas.junk@intevation.de> |
---|---|
date | Tue, 28 Aug 2018 11:50:13 +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 ```