Mercurial > gemma

comparison README.md @ 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 9d6ba97a31d2
children 0f78b13f4a9a
comparison
equal deleted inserted replaced
329:71970f03c9e8 330:fd04bccae6ca
30 - Standard case: as user "postgres", in the top level directory of the 30 - Standard case: as user "postgres", in the top level directory of the
31 repo run: 31 repo run:
32 32
33 ## Running gemma 33 ## Running gemma
34 34
35 - In the top level directory of the repo run: 35 - Best is to create a configuration file. Copy the example from
36 `./cmd/gemma/gemma -s session.data -w ./web` 36 `cmd/gemma/gemma.toml.example` to get started:
37 ```
38 cp cmd/gemma/gemma.toml.example gemma.toml
39 ```
37 40
38 - To listen on a specific port and interface: 41 - Edit `gemma.toml`, some parameters you propably want to change:
39 ``` 42
40 ./cmd/gemma/gemma -s session.data -w ./web \ 43 * `host` and `port` to make gemma listen on a public interface
41 --host 192.168.46.72 -p 8088 44 * `service-password` to match the password for "gemma_service" user
42 ``` 45 of your database.
43 46
44 - `./cmd/gemma/gemma -h` gives you an overview of more available 47 - `./cmd/gemma/gemma -h` gives you an overview of more available
45 options. 48 options.
49
50 - Then start gemma:
51 ```
52
53 ```